DATA NETWORKING PRODUCTS PLANNING GUIDE

Data Networking ProductsPlanning Guide

255-100-230 ISS4

Copyright 1998 Lucent TechnologiesAll Rights ReservedPrinted in USA

Billdats, Datakit, DEFINITY, 5ESS, and StarKeeper are registered trademarks of Lucent Technologies.SecurID is a trademark of Security Dynamics Technologies, Inc.

The information in this document is subject to change without notice.Lucent Technologies assumes no responsibility for any errors that

may appear in this document.

________________Contents

Preface xiiiImportant Notice xiiiNew Material xivDocument Organization xivRelated Documentation xvi

Overview 1-1Network Planning 1-3Node Planning 1-4Concentrator and Multiplexer Planning 1-7Trunk Module Planning 1-9Interface Modules and Services Planning 1-10Network Management Planning 1-11Operational Features Planning 1-11Migration and Interworking 1-14

Node 2-1Node Types 2-3Critical Equipment Design 2-12Shelf Design 2-17Module Placement 2-31Equipment Specifications and Compliances 2-33Site Preparation 2-39

Concentrators and Multiplexers 3-1Concentrator and Multiplexer Types 3-3Critical Equipment Design 3-5Cabinet Design 3-8Electrical Specifications and Compliances 3-12Site Preparation 3-17

Data Networking Products Planning Guide, Issue 4 iii

________________Trunks 4-1

Trunk Types 4-3Trunk Design Issues 4-10Interworking 4-15Electrical Specifications and Compliances 4-17

Interface Modules 5-1Interface Module Types 5-3General Interface Module Design Issues 5-12Specific Interface Module Design Issues 5-14AI 5-15CPM 5-19CPY1 (SAM16) 5-19DKAP 5-20FRM 5-21FRM-M2 5-34GAR 5-49LPM 5-50MSM 5-57SYNC8 5-58TERM32 5-60TSM8 5-61TSM-T1 5-62TY 5-82X.25 5-84X.25P 5-85X.75 5-97Interworking 5-102Electrical Specifications 5-108

Connection-Oriented Network Services 6-1Fundamentals 6-3Address Planning 6-5Routing Strategies 6-6Endpoint Routing Plan 6-9

Addresses and Groups 7-1Service Addresses 7-3Physical Addresses 7-14Combination Addresses 7-15Groups 7-16

iv Data Networking Products Planning Guide, Issue 4

________________Routing 8-1

Routing Plans 8-3Trunk Groups 8-9Alternate Routing 8-11Interworking 8-17

Security 9-1Overall Security Planning 9-3Security Features 9-6Security Planning Examples 9-27

Database 10-1Basic Structure 10-3Database and System Limits 10-4

Appendix A. Recommended Spare Parts A-1

Appendix B. Database Design Forms B-1

Index I-1

Data Networking Products Planning Guide, Issue 4 v

________________Figures

2-1. A Virtual Circuit 2-62-2. BNS-2000 VCS Bus Architecture Example 2-72-3. BNS-2000 Standard Star Architecture Example 2-92-4. BNS-2000 Extended Star Architecture Example 2-102-5. BNS-2000 VCS Maximum Node Shelf Arrangement 2-182-6. Maximum Configuration of Series M1 Shelves in a BNS-2000 Node 2-212-7. Maximum Configuration of Series M2 Shelves in a BNS-2000 Node 2-222-8. I/O Cable Egress from Series M1 and M2 Shelves 2-402-9. I/O Cable Egress from Base Power Units 2-412-10. Single BNS-2000 VCS Series M1 Control Shelf on a Power Base Unit 2-422-11. BNS-2000 VCS Series M1 Shelves on Base Power Units 2-432-12. Minimum BNS-2000 Node with Series M1 and M2 Shelves on Base

Power Unit 2-442-13. Four BNS-2000 Shelves on Base Power Unit 2-452-14. Customer Premises Floor Plan 2-472-15. Four BNS-2000 or BNS-2000 VCS Shelves Mounted in a CO Frame 2-482-16. CO Floor Plan—Single CO Frame 2-492-17. CO Floor Plan—Two CO Frames 2-50

3-1. BNS-2000 MPC Slot Allocation 3-93-2. SAM16 Rear View (Dual RS-232-C Link Option) 3-103-3. SAM64 Front and Rear Views 3-113-4. SAM504 Multiplexer Shelf 3-123-5. BNS-2000 MPC Front View 3-183-6. SAM504 3-193-7. SAM504 Floor Plan 3-203-8. VDM-SAM504 3-213-9. Configuration with VDM Cabinets 3-223-10. SAM64 3-233-11. SAM16 3-24

4-1. Trunk Selection Guidelines by Node Type 4-74-2. Trunk Selection Guidelines for a Specific Traffic Type 4-84-3. Link Selection Guidelines for a SAM 4-94-4. Trunk Selection Guidelines for a BNS-2000 Series M2 Shelf 4-10

vi Data Networking Products Planning Guide, Issue 4

________________5-1. AI-T3 Full Duplex Performance 5-175-2. CIR, Be Rate, and Discard Rate 5-265-3. CIR, Be Rate, and Discard Rate 5-415-4. TSM-T1 Module Throughput as a Function of Frame Size 5-635-5. TSM-T1 GOS3 and GOS5 Performance Over Trunks (300-byte

Frames) 5-695-6. TSM-T1 GOS3 and GOS5 Performance Over Trunks (1000-byte

Frames) 5-705-7. Intranodal Point-to-Point TSM-T1 Throughput as a Function of Frame

Size 5-735-8. Network Transport Delay via a TSM-T1 for a Window 5-805-9. X.25P Throughput as a Function of Line Speed (per Packet Size) 5-90

6-1. Connection Services Sample Network 6-7

8-1. Hub and Leaf Nodes in a Hierarchy 8-48-2. Hub and Leaf Levels in Default Routing Hierarchy 8-58-3. Non-Hierarchical Network Example 8-88-4. Two Trunks to the Same Node 8-108-5. Three Trunks to Different Nodes 8-108-6. Alternate Routing Example 8-118-7. Crankback 8-148-8. Route Advance 8-15

9-1. Network Access Restriction 9-79-2. Originating Group Security 9-89-3. Call Screening Security 9-129-4. CUG Security 9-159-5. CUG with Incoming Access 9-169-6. CUG with Outgoing Access 9-179-7. Incoming and Outgoing Calls Barred 9-209-8. Security System Configuration with Central Security Administration 9-239-9. Call Back Modem Security 9-259-10. Originating Group Security Example 9-289-11. CUG Security Example 9-309-12. Trunk Call Screening Example 9-33

Data Networking Products Planning Guide, Issue 4 vii

________________Tables

1-1. Network Building Blocks 1-31-2. Node Service Differences 1-51-3. Supported Node Equipment 1-61-4. Supported Concentrator and Multiplexer Equipment 1-81-5. Trunk Module Summary 1-91-6. Interface Module Services 1-101-7. Security Options 1-13

2-1. Node Capacities 2-42-2. Supported CCM Single and Dual Configurations 2-142-3. Supported ECPU Single and Dual Configurations 2-152-4. Control Computer Configurations Features/Functions Supported 2-162-5. BNS-2000 VCS Series M1 Shelf Combinations in a Node 2-172-6. Series M1 and Series M2 Shelf Combinations in a BNS-2000 Node 2-202-7. Series M1 Shelf Number and Module Address Correspondences 2-252-8. Series M1 and Series M2 Shelf Number and Module Address

Correspondences 2-272-9. Number of User Interface Modules in a Node 2-312-10. Equipment Size, Weight, and Cooling 2-332-11. Node Electrical Service Requirements 2-342-12. Node Total Power Consumption 2-352-13. Node Module and I/O Board Electrical Service Requirements 2-362-14. Environmental Operating Limits 2-372-15. Electromagnetic Compliances 2-372-16. Safety Compliances 2-382-17. Input Power Compliance 2-38

3-1. Concentrator and Multiplexer Architecture Overview 3-43-2. Concentrator and Multiplexer Interface Overview 3-43-3. Concentrator and Multiplexer Link Interfaces 3-63-4. Concentrator/Multiplexer Cabinet Distinctions 3-83-5. Concentrator Size, Weight, and Cooling 3-133-6. International Input Power Compliance 3-133-7. Concentrator and Multiplexer Electrical Service Requirements 3-143-8. BNS-2000 MPC Total Power Consumption 3-153-9. BNS-2000 MPC Module and I/O Board Electrical Service

Requirements 3-15

viii Data Networking Products Planning Guide, Issue 4

________________3-10. Environmental Operating Limits 3-163-11. Electromagnetic Compliances 3-163-12. Safety Compliances 3-17

4-1. Trunk Connectivity and Speeds 4-44-2. Trunk Module Channels 4-54-3. Trunk Module and I/O Board Port Connections 4-64-4. Trunk Module Availability and Compatibility 4-154-5. Trunk Distance Limits 4-174-6. Trunk Module and I/O Board Electrical Service Requirements 4-194-7. Electrical/Mechanical Connection Standard Compliances 4-20

5-1. Interface Module Services 5-45-2. Asynchronous Module Characteristics 5-55-3. Customer Programmable Module 5-65-4. LAN Interconnect Module Characteristics 5-65-5. Multiplexed Host Characteristics 5-75-6. SMDS Access Interface (AI) Module Characteristics 5-75-7. Special Module Characteristics 5-85-8. Standards Module Characteristics 5-85-9. Synchronous Module Characteristics 5-95-10. Interface Module and I/O Board Port Connections 5-105-11. GOS Levels 5-125-12. SMDS Access Class and Sustained Information Rate 5-155-13. Access Class Identifiers and Sustained Information Rates 5-165-14. FRM Throughput and Frame Size 5-225-15. T1 Small Frame Performance 5-355-16. E1 Small Frame Performance 5-365-17. SYNC8 Port and CU Combinations 5-585-18. SYNC8 Possible Configuration 5-595-19. Average Traffic per Port and Number of Ports for TSM-T1 5-645-20. TSM-T1 Frame Size and Number of Broadcast Channels 5-665-21. TSM-T1 Processing Delays 5-765-22. TSM-T1 Broadcast Delays 5-765-23. Trunk Processing Delays for a TSM-T1 5-775-24. Module Interworking with a TSM-T1 5-815-25. TY12 Throughput 5-825-26. TY6 Throughput 5-835-27. X.25 Planning Factors 5-845-28. X.25P Planning Factors 5-855-29. Recommended Number of Ports For Combinations of Line Speed

and Packet Size 5-86

Data Networking Products Planning Guide, Issue 4 ix

________________5-30. Recommended Channels per X.25P Port 5-875-31. Recommended Maximum Number X.25P Channels 5-885-32. X.25P Packet Sizes 5-895-33. Maximum Sustained Performance of V.35 X.25P Ports 5-915-34. Maximum Sustained Performance of RS-232-C X.25P Ports 5-925-35. Recommended V.35 Throughput for an X.25P Module 5-935-36. Recommended RS-232-C Throughput for an X.25P Module 5-935-37. Maximum Sustained Performance of PAD Ports for an X.25P Module 5-945-38. Recommended PAD Port Throughput for an X.25P Module 5-955-39. Network Delay as a Function of Packet Size 5-965-40. Bi-directional X.75 Module Throughput in Terminate Mode 5-985-41. One-way X.75 Throughput for Packet Assembly 5-995-42. One-way X.75 Throughput for Packet Disassembly 5-1005-43. Configurable Channels per X.75 Port 5-1015-44. Maximum Number of Configurable X.75 Channels 5-1015-45. Asynchronous Interworking 5-1035-46. LAN Interconnect Interworking 5-1035-47. Multiplexed Host Access Interworking 5-1045-48. SMDS Interworking 5-1055-49. Special Purpose Interworking 5-1055-50. Standards Interworking 5-1065-51. Synchronous Interworking 5-1075-52. Interface Module and I/O Board Electrical Service Requirements 5-108

7-1. Address Types and Formats 7-57-2. Comparison of Mnemonic and X.121 Numeric Address Levels 7-77-3. Call Routing Scenarios 7-13

8-1. Information Requirements for Default Routing at Nodes 8-68-2. Routing Choices for Nodes at Each Level 8-7

9-1. Special Characters used in Originating Group Security Patterns 9-99-2. Originating Group Access Requirements 9-289-3. CUG Access Requirements 9-31

x Data Networking Products Planning Guide, Issue 4

________________A-1. Series M2 Shelf Common and Critical Modules A-2A-2. Series M2 Shelf Miscellaneous Spares A-2A-3. Series M1 Shelf Common and Critical Modules A-3A-4. Series M1 Shelf Miscellaneous Spares A-4A-5. Series M1 Shelf Miscellaneous Spares A-5A-6. BNS-2000 MPC Common and Critical Modules and Miscellaneous

Parts A-6A-7. Base Power Unit Spares A-6A-8. SAM16 Spares A-7A-9. SAM64 Spares A-7A-10. SAM504 Spares A-8A-11. Trunk Module Board Spares A-9A-12. Trunk I/O Distribution Board Spares A-10A-13. Interface Module Board Spares A-11A-14. Interface I/O Distribution Board Spares A-12

Data Networking Products Planning Guide, Issue 4 xi

________________Preface

The Data Networking Products Planning Guide gives the information necessary for planning aBNS-2000 and/or a BNS-2000 VCS network. It is intended to assist network planners in theoverall planning and management of a network and its installation. Information is provided onthe hardware and software that can be used to construct different types of data networks thatsupport a range of configurations and a variety of services.

A complete description of BNS-2000, BNS-2000 VCS, and additional Data Networking Productsand the services they provide is given in the BNS-2000 System Description. In particular, theSystem Description also includes information on training and start-up services.

The Data Networking Products Session Maintenance Guide gives information for planning anetwork using the session maintenance feature. In addition, planning for a SwitchedMultimegabit Data Service (SMDS) network is included in the BNS-2000 SMDS Guide.

Important Notice

As of January 1997, Lucent Technologies has merged Datakit II VCS and MPC15 into oneBNS-2000 hardware platform. The new name for Datakit II VCS is BNS-2000 VCS; the newname for the MPC15 is BNS-2000 MPC. Ordering will be simplified through the use of one (1)"J" drawing for initial orders. There will be different software for the BNS-2000 and BNS-2000VCS but one (1) BNS-2000 documentation set that will include the necessary information for theBNS-2000, BNS-2000 VCS, and BNS-2000 MPC. Existing Datakit II VCS and BNS-2000customers will receive the new documentation set when they purchase upgrades.

The BNS-2000 hardware platform will consist of the following options:

BNS-2000 — is the BNS-2000 M1/M2 cabinet configuration supporting both low-speed (M1)and high-speed (M2) modules. This configuration will require BNS-2000 software.

BNS-2000 VCS — is the BNS-2000 VCS M1-only cabinet configuration supporting low-speed (M1) modules. The M1 cabinet will contain clock/repeater modules as opposed toCIM/CTRM modules contained in BNS-2000 M1 cabinets. M2 cabinets are not required.This configuration requires BNS-2000 VCS/Datakit II VCS R6.0 software.

BNS-2000 MPC — is the BNS-2000 MPC M1 Multipurpose Concentrator cabinetconfiguration.

Data Networking Products Planning Guide, Issue 4 xiii

Preface________________BNS-2000 Release 4.0 documentation will be updated to include information on the BNS-2000,BNS-2000 VCS, and BNS-2000 MPC.

All BNS-2000 offerings described above are managed by StarKeeper II Network ManagementSystem (NMS). (When configuring BNS-2000 VCS, customers select "Datakit II VCS" as thenode option.)

BNS-2000 training courses will be updated to include information on the BNS-2000 VCS andBNS-2000 MPC offerings.

New Material

This issue of the Planning Guide documents the hardware and software enhancements forBNS-2000 Release 5.0. Two additional Series M2 Extension Shelves can be added to a nodeconfiguration, which raises the maximum number of Series M2 Extension Shelves from three tofive. (Therefore, the total number of Series M2 Shelves, which include both Switch and ExtensionShelves, is now six; however, the node backplane capacity does not increase with the additionalshelves—it remains the same.) Along with this hardware configuration enhancement, an upgradeto the Stratum 4 Clock offers industry compliant clocking and synchronization redundancy, soany failed removeable unit can be replaced while the BNS-2000 node is up and running.

Document Organization

The document is organized as follows:

Overview This chapter provides a broad method for planning a data network.

Node This chapter explains planning and design aspects of BNS-2000 andBNS-2000 VCS nodes, including node types, cabinet configurationguidelines, specifications such as height and weight, electricalrequirements, and capacities. It also provides design issues andguidelines for site planning.

Concentrators andMultiplexers

This chapter explains how to plan a network that includes theBNS-2000 Multipurpose Concentrator (MPC) andSynchronous/Asynchronous Multiplexers (SAMs). It gives MPCand SAM specifications such as height and weight, electricalrequirements, and capacities. It also provides design issues andguidelines for site planning.

Trunks This chapter provides physical and hardware-related details for trunkmodules including distance limits, interface standards, and electricalrequirements and it covers design issues and interworking.

xiv Data Networking Products Planning Guide, Issue 4

Preface________________Interface Modules This chapter explains physical and hardware-related information on

interface modules. It includes general design issues that affect allmodules and specific design issues that affect a particular module.Module electrical requirements and interworking information is alsoincluded.

Connection-OrientedNetwork Services

This chapter should be used as a starting point when planning theservices offered by a connection-oriented network. It describesaddress, routing, and security plans for a connection-orientednetwork service (CONS) environment. It includes an overview of allconcepts presented and a simple example to help explain thoseconcepts.

Addresses and Groups This chapter explains the addressing schemes used to identifyhardware components within the network. It also gives detailedexplanations of the types of groups that can be administered.

Routing This chapter provides physical and software-related details forrouting in a CONS environment. The chapter includes informationon routing network topologies, routing plans, trunk groupconfigurations, and alternate routing.

Security This chapter explains all aspects of security for a connection-orientednetwork.

Database This chapter provides guidance on the major components of thedatabase, how to determine if database planning is needed, and thetools and techniques available to assist in this planning.

Appendix A.Recommended SpareParts

This appendix lists the recommended number of spare parts that mustbe kept on hand for each piece of equipment in order to maintainservice. This appendix is especially useful for sites that do not havea maintenance contract.

Appendix B. DatabaseDesign Forms

This appendix provides forms for gathering and organizinginformation to administer the database.

Data Networking Products Planning Guide, Issue 4 xv

Preface________________Related Documentation

BNS-2000 Publications describes the complete documentation sets available for the product line.(See the inside front cover for ordering information.)

The following documents provide general information about the features and capabilities of theproduct or information directly related to network planning, configuration, and installation:

BNS-2000 System Description

BNS-2000 Node Reference

The following specialized documents are companion documents to this guide:

BNS-2000 SMDS Guide

Datakit II VCS to BNS-2000 Conversion Guide

Data Networking Products Cabling Guide

Data Networking Products Commands Reference

Data Networking Products Multipurpose Concentrator Reference

Data Networking Products Ordering Guide

Data Networking Products Session Maintenance Guide

Data Networking Products Synchronous/Asynchronous Module Reference

Additional information for any trunk or interface module mentioned can be found in theappropriate reference document for that module.

xvi Data Networking Products Planning Guide, Issue 4

________________Overview

Network Planning 1-3

Node Planning 1-4Node Performance and Capacity 1-4Node Services 1-5Node Equipment 1-6Node Design and Planning Issues 1-6Redundancy Options and Node Availability 1-7

Concentrator and Multiplexer Planning 1-7Concentrator and Multiplexer Equipment 1-8Concentrator and Multiplexer Design and Planning Issues 1-8

Trunk Module Planning 1-9

Interface Modules and Services Planning 1-10Feature Packages 1-11

Network Management Planning 1-11

Operational Features Planning 1-11Addressing 1-12Routing 1-12Security 1-13Database 1-13

Migration and Interworking 1-14Migration 1-14Interworking 1-15

Data Networking Products Planning Guide, Issue 4

________________Overview

This chapter provides an overview of the entire network planning process. Detailed explanationsof the concepts touched upon in this chapter can be found in the following chapters orappendixes.

Network Planning

Network planning requires detailed knowledge of the interfaces and services required to besupported at various physical locations, as well as the expected growth of those services overtime. This type of information is necessary to allow the network planner to make decisions on thelocation of nodes, concentrators, multiplexers, trunks, and interface modules. In general, thisiterative process has tradeoffs with equipment, facility costs, and future growth.

A data network constructed with Data Networking Products nodes consists of the building blocksshown in the following table.

TABLE 1-1. Network Building Blocks

_ __________________________________________________________________________Building Block Description_ ___________________________________________________________________________ __________________________________________________________________________

The node is the most basic building block of a data network. It providescall processing, and the operations, administration, and maintenancecontrol needed for data switching. Interface modules within the nodeprovide data services. Networking is provided via facility trunks toconcentrators, multiplexers, and other nodes.

Nodes

_ __________________________________________________________________________Concentrators and multiplexers provide concentration of services atlocations remote from the node. Concentrators and multiplexers combinetraffic from multiple interfaces and transfer the information over a singlehigher speed link to the node.

Concentrators and Multiplexers

_ __________________________________________________________________________Trunk modules provide high speed interfaces between a node and othernodes, concentrators, and multiplexers.

Trunk Modules

_ __________________________________________________________________________Interface modules provide the data service interface from the customer tothe node, concentrator, or multiplexer. A variety of interface modulessupport a range of data services.

Interface Modules

_ __________________________________________________________________________

Data Networking Products Planning Guide, Issue 4 1-3

Overview________________Node Planning

Two basic node types are supported in the Data Networking Products family:

BNS-2000 nodes

BNS-2000 VCS nodes

These node types are compatible with each other and can be combined in a single network. Inaddition, they are compatible and can interwork with previous network releases and with aDatakit VCS or Datakit II VCS network, a BNS-1000 network, and an Information SystemsNetwork (ISN).

These node types have many services and components in common, including numerous interfacemodules. The primary factors in choosing between these node types are the performance andcapacity requirements and the services required on the network.

Node Performance and Capacity

Both the BNS-2000 and BNS-2000 VCS nodes switch data using packet switching. The interfacemodules segment the data from the customer into small packets of data and transmit theinformation across the node via the node backplane.

The backplane of a BNS-2000 VCS node switches fixed-length data packets at 8 Mbps, or over44,000 packets per second. Actual data throughput is greater than 5.6 Mbps. Each packetcontains up to 16 bytes of user data.

The backplane of a BNS-2000 node provides 216 Mbps of bandwidth for transport of variablelength segments of data. A segment can vary in length from 20 to 56 octets which can hold apayload of 16 to 53 octets (plus segment header information). This is equivalent to a segmenttransfer rate of 1.2 million segments per second for the smallest segment and 428,571 segmentsper second for the largest segment.

Although BNS-2000 is optimized for transport of 53-byte cells, it also supports variable-lengthsegments. The net effect of variable-size segments is that node bandwidth is optimized byadapting the segment size to its payload size, and the amount of buffering required by interfacemodules is minimized because null word payloads are not stored. This characteristic results inminimal delay, comparable in performance to direct cable connections between twocommunicating endpoints.

This bandwidth difference is one major factor in deciding on use of the BNS-2000 VCS nodeverses the BNS-2000 node. For nodes requiring high bandwidth applications with an aggregateaverage bandwidth for all interfaces in excess of 4 MB per second, a BNS-2000 node isrecommended. Otherwise, a BNS-2000 VCS node can be used. Note that because packetswitching is employed, peak traffic is normally not an issue with either node.

1-4 Data Networking Products Planning Guide, Issue 4

Overview________________For BNS-2000 and BNS-2000 VCS networks, performance degradation under overloadconditions is handled gracefully; however, great care should be taken not to overload thebackplane’s capacity when engineering the network. When an overload does occur, throughputat the Switch increases with an increased traffic load until it reaches a maximum. It then remainsconstant until the traffic load decreases.

For all network nodes, the round-trip delay through a single node is about 50 milliseconds, witheach additional node adding as little as two—but no more than 10—milliseconds. This delay stillallows data to travel through multiple nodes and meet strict echoplex application delayrequirements. The actual end-to-end delay is a function of the distance between nodes, trunkloading, modems, use of routers, speed of facilities, and other considerations.

Node Services

BNS-2000 and BNS-2000 VCS nodes support many common services; however, some servicesare not supported in both nodes and thus affect the choice of node type. The services that are notsupported in both nodes are summarized in the following table.

TABLE 1-2. Node Service Differences

______________________________________________________________________________Service Description____________________________________________________________________________________________________________________________________________________________

Only BNS-2000 supports the T3A and E3A trunks, which connect toAsynchronous Transfer Mode (ATM) switches. The Trunk-T3A andTrunk-E3A support T3 and E3 transmission rates.

ATM Switch Connections

______________________________________________________________________________Only BNS-2000 supports CLNS such as Switched Multimegabit DataService (SMDS). If SMDS is required, all nodes havingconnectionless interfaces or switching connectionless traffic must beBNS-2000 nodes. BNS-2000 VCS nodes cannot be in the datatransfer path, although they can be interconnected to the BNS-2000nodes for other services.

Connectionless Network Service (CLNS)

______________________________________________________________________________Only BNS-2000 supports the FRM-M2, which brings frame relayservice to BNS-2000 nodes via the Series M2 Shelf.

Frame Relay Enhanced Services

______________________________________________________________________________Only BNS-2000 supports internodal trunk speeds of T3 and E3 rates.If T3 and E3 rates are required, BNS-2000 nodes must be used ateach end of the trunk.

T3 or E3 Trunks

______________________________________________________________________________

All other features and interface services are provided on both BNS-2000 and BNS-2000 VCSnodes.


Overview________________Node Equipment

BNS-2000 VCS network nodes consist of Series M1 Shelves; BNS-2000 network nodes consist ofSeries M1 Shelves and Series M2 Shelves. The node equipment options supported aresummarized in the following table.

TABLE 1-3. Supported Node Equipment

_ ________________________________________________________________________________Equipment BNS-2000 BNS-2000 VCS Description_ _________________________________________________________________________________ ________________________________________________________________________________

Basic shelf/cabinet supporting common interfacemodules and trunks.

Series M1 Shelf √ √

_ ________________________________________________________________________________200 MB shelf supporting only specific BNS-2000interface module and trunks.

Series M2 Shelf √

_ ________________________________________________________________________________Mounting frame and power for -48V DC COapplications.

Central Office (CO) Frame √ √

_ ________________________________________________________________________________Base Power Unit √ √ Power unit for AC customer premises

(CP) applications._ ________________________________________________________________________________

Node Design and Planning Issues

Many design and planning issues are associated with nodes. They are described in detail in thefollowing chapters and some more important issues are summarized here.

Equipment Specifications and Site Requirements

The physical dimensions of each piece of networking equipment and the site chosen for theequipment must be considered when locating nodes. In addition, the equipment’s capacity tohouse modules that provide critical and end user services and that offer connectivity to othernodes and networks must be carefully planned.

Power

The power issues that should be taken into consideration when planning a node include thefollowing:

electrical service requirements at each node site

power consumption of each piece of networking equipment

total power consumption of each critical, trunk, and interface module residing in a node

power supply options used in the configuration


Overview________________Redundancy Options and Node Availability

Various redundancy options that affect node availability are supported. They are the following:

optional automatic recovery to redundant Control Computer

optional automatic switchover to standby switch

optional automatic call rerouting around failed trunk facilities

automatic alternate routing of calls during setup

In addition, the star architecture of BNS-2000 (Series M1 shelves connected separately to SeriesM2 Switch Shelf) ensures high node availability.

Two node Control Computer complex configurations are supported, and the choice depends onthe requirements for availability of critical control modules, remote maintenance, and automaticcutover if critical hardware fails. High availability is further guaranteed with the Maintenanceand Redundancy Control (MRC) function, redundant power supplies, and redundant switches.

With BNS-2000 central office (CO) cabinets, a redundant power feed is also provided. Any oneof the four power feeds can fail without affecting the node operation.

Concentrator and Multiplexer Planning

The Data Networking Products family supports the following two types of concentrators andmultiplexers:

BNS-2000 Multipurpose Concentrator (MPC)

Synchronous/Asynchronous Multiplexer (SAM)

These concentrators and multiplexers, which are compatible with each other and can be combinedin a single network, support common services and components. The primary factors to considerwhen choosing between these concentrator types are the number and type of interfaces required.


Overview________________Concentrator and Multiplexer Equipment

Various concentrator and multiplexer equipment options are supported and are summarized in thefollowing table.

TABLE 1-4. Supported Concentrator and Multiplexer Equipment

_ ________________________________________________________________________________Equipment BNS-2000 BNS-2000 VCS Description_ _________________________________________________________________________________ ________________________________________________________________________________

Concentrator supporting 15 slots for most interfacemodules

BNS-2000 MPC √ √

_ ________________________________________________________________________________Multiplexer supporting 16 ports for synchronous orasynchronous interfaces

SAM16 √ √


SAM64 √ √


SAM504 √ √

_ ________________________________________________________________________________Multiplexer supporting 504 voice/data multiplexer (VDM)ports for synchronous or asynchronous interfaces

VDM-SAM504 √ √

_ ________________________________________________________________________________

For sites requiring only asynchronous or transparent synchronous services, a SAM can be used.For sites requiring other user services, an MPC or a node must be used.

Concentrator and Multiplexer Design and Planning Issues

Many design and planning issues are associated with the concentrators and multiplexers. Theyare described in detail in the following chapters and some more important issues are summarizedhere.

Equipment Specifications and Site Requirements

The physical dimensions of each piece of networking equipment and the site chosen for theequipment must be considered when locating concentrators and multiplexers. In addition, theequipment’s capacity to house modules that supply critical and end user services and that offerconnectivity to nodes must be carefully planned.


Overview________________Power

The power issues that should be taken into consideration when planning a concentrator ormultiplexer include the following:

electrical service requirements at each concentrator or multiplexer site

power consumption of each piece of networking equipment

total power consumption of each critical, trunk, and interface module residing in aconcentrator or multiplexer

power supply options used in the configuration

Redundancy Options

The number of facility links from the concentrator or multiplexer to the node can be an issue. Adual link can be supported with some SAM configurations and all MPC configurations.

Trunk Module Planning

Several trunks are supported from the node to other nodes, multiplexers, or concentrators. Thechoice of trunk type depends on many factors—the major factors include the throughput,distance, and speed required to carry the traffic generated by the node, multiplexer, and/orconcentrator; the type of node, multiplexer, and/or concentrator being connected; and the type oftraffic on the trunk.

The major classes of trunks supported are summarized in the following table.

TABLE 1-5. Trunk Module Summary

_ ___________________________________________________________________Type Description_ ____________________________________________________________________ ___________________________________________________________________

Trunk interfaces via EIA RS-232-C and V.35 ports at speeds ranging from 2.4Kbps to 2.048 Mbps provide wire trunks to other nodes, multiplexers, andconcentrators.

Wire Trunks

_ ___________________________________________________________________Trunk interfaces via fiber connections at speeds up to 8 Mbps to local nodes,concentrators, and multiplexers.

Fiber Trunks

_ ___________________________________________________________________Trunk interfaces via coaxial cable connections at E3/T3 rates to BNS-2000nodes.

Coaxial Trunks

_ ___________________________________________________________________


Overview________________Interface Modules and Services Planning

The interface modules supported by Data Networking Products nodes provide numerous end userand shared services. The network planner must decide which end user services the network is toaccommodate. These services are summarized in the following table.

TABLE 1-6. Interface Module Services_ ____________________________________________________________________________

Service Description_ _____________________________________________________________________________ ____________________________________________________________________________Asynchronous interface via EIA RS-232-C ports at speeds ranging from75 bps to 115.2 Kbps to computers, terminals, printers, modems, and hostcomputer ports. XON/XOFF, EIA, or no flow control options areprovided. Odd, even, mark, or no parity is supported.

Asynchronous Interface

_ ____________________________________________________________________________A programmable interface that provides 64 KB or ROM and 2 MB ofRAM for specialized customer applications such as context switching,protocol conversion, or security screening programs.

Customer Programmable

_ ____________________________________________________________________________High-speed frame relay interfaces for LANs via V.35 connections atspeeds up to 2.048M and/or direct Ethernet LAN interfaces for TCP/IPhosts via 10Base-T interface. A related product line, the LANCommunications Systems (LCS), implements LAN interconnections.

LAN Interconnect Services

_ ____________________________________________________________________________Multiplexed host interfaces via RS-232-C and fiber connections forcurrently supported Lucent Technologies computer systems and vendorcomputer systems.

Multiplexed Host Interface

_ ____________________________________________________________________________Connectionless, packet-switched service for BNS-2000 that includesinterfaces providing T1/E1/E3/DS3 connections at speeds up to 44.736Mbps. Includes a specialized interface to provide the capabilities of aGroup Address Agent (GAA), a 32-port SMDS switch that supports DataExchange Interface/Subscriber Network Interface (DXI/SNI)specification, and support for subscriber bridges and/or routers.

SMDS

_ ____________________________________________________________________________Interfaces that support the service provider, Operations Systems (OSs),including telemetry support between OS hosts and analog switches at1200 bps and BX.25 Issue 2 protocol conversion between OS hosts anddigital switches at speeds of 2400 bps or 9600 bps.

Special Purpose

_ ____________________________________________________________________________Access to X.25 public data networks (PDNs) or packet-switched publicdata networks (PSPDNs) via national or international gateways throughRS-232-C or V.35 connections at speeds ranging up to 64 Kbps (X.25) orup to T1/E1 rates (X.25P/X.75).

Standards

_ ____________________________________________________________________________Synchronous interface via EIA RS-232-C and V.35 ports at speedsranging from 110 bps to 2.048 Mbps to various terminals and hosts.Protocols supported include HDLC, SDLC, DDCMP, BSC,Burroughs/NCR Poll/Select, and UNISCOPE.

Synchronous Transport Services

_ ____________________________________________________________________________Individual 3270-type terminals with switched access to 3270-type hostsvia RS-232-C or V.35 connections.

Switched Bisynchronous Services

_ ____________________________________________________________________________


Overview________________Feature Packages

BNS-2000 and BNS-2000 VCS offer an assortment of feature packages that enable specificnetwork, node, and end-user capabilities; choices depend on the services required for a node.

The components comprising the feature packages supported for BNS-2000 and BNS-2000 VCSdiffer. The System Description fully explains the equipment and services provided by eachpackage. The overall components of all packages are explained, from a planning perspective, inthe following sections and chapters of this document.

Network Management Planning

The StarKeeper II Network Management System (NMS) can be used for centralized networkadministration and management. The StarKeeper II NMS system supports network managementfeatures that are especially valuable to networks that consist of more than a few nodes.

StarKeeper II NMS is required if the following functions are necessary in the network:

centralized node monitoring

centralized alarms, performance, and billing data collection; some measurements are onlyavailable via StarKeeper II NMS

Session Maintenance trunk administration

SMDS logical resources administration or billing in BNS-2000 networks

Refer to the StarKeeper II NMS Planning Guide for more information about how to plan anetwork that intends to use StarKeeper II NMS.

Operational Features Planning

Data Networking Products nodes support a range of operational features that are necessary ordesirable in data networks. Planning is especially important with the following features:

addressing

routing

security

database management


Overview________________Addressing

Both BNS-2000 and BNS-2000 VCS support a network addressing scheme in which the addressof any destination endpoint can be represented in mnemonic form, numeric form, or bothmnemonic and numeric forms.

The network planner must devise an addressing scheme that accommodates all network nodes andtheir connected end devices. The major decisions that must be made when planning a networkaddressing scheme are the following:

Mnemonic or Numeric Addressing

Mnemonic addresses identify endpoints within a network and designate special addresses forspeedcalls, aliases, directory assistance, and billing.

Numeric addresses are assigned to network destinations (endpoints) that connect to 5ESSswitch endpoints, public data network (PDN) endpoints, packet-switched public data networks(PSPDNs) endpoints, or X.25 hosts. They can also be assigned to endpoints that originatecalls.

Type of Numeric Addressing

Numeric addresses conform to three standard numbering plans for national and internationalcall addressing and routing. Each numbering plan serves a particular geographical area and/oris designed to accommodate a special type of service. The network planner must know if thearea to be served is within North America or outside of North America, what type of datanetwork is being connected, and what services must be brought to the users.

Routing

Once an addressing and group scheme is decided upon, the network topology must be defined,addresses must be assigned, and addresses must be associated with local and trunk groups. Thepaths to and from each node in the network must be defined for every valid endpoint address.This process is called routing.

When devising a routing strategy, the network planner must decide which routing strategy to use.The choices are the following:

hierarchical default routing

full (non-default) routing

a variation hierarchical default routing and/or full (non-default) routing

The routing strategy selected often depends on the size of the network and which end user andshared services must be made available to which groups.


Overview________________Security

Planning network security involves the following:

devising a security plan for the entire network

devising a security plan for each node

understanding how security features administered for each node interact when combined

The following table summarizes the network and node security options available.

TABLE 1-7. Security Options

_____________________________________________________________________________Security Option Description__________________________________________________________________________________________________________________________________________________________

Restricts calls originating from a CPM or outgoing on a trunk. Call Screening_____________________________________________________________________________Restricts incoming/outgoing calls to CUG members. Closed User Group (CUG)_____________________________________________________________________________Restricts access to node console. Console Security_____________________________________________________________________________Customer programmable security software. DKAP_____________________________________________________________________________Restricts connections between logical and physical ports. LPM port screening_____________________________________________________________________________Restricts access to the network DESTINATION prompt. Network Access_____________________________________________________________________________Provides access control, user identification and authentication, andauditing functions.

Network Access Control System

_____________________________________________________________________________Restricts access to each destination according to the originatinggroup identity.

Originating Group

_____________________________________________________________________________Supports incoming/outgoing calls barred. X.25_____________________________________________________________________________Includes CUG indication, access indication, and traffic agreementchecking.

X.75

_____________________________________________________________________________

Database

When planning a database, the network planner should consider the following:

The number of physical entities (nodes, concentrators, trunks, and interface modules) to beconfigured in the network and the number of logical elements (addresses, groups, profiles, andgateways) to be administered for the entire network must be estimated.

This estimate must be compared to the predetermined database limits established.

The actual number of physical entities and logical elements to be administered in the databasemust be adjusted to the predetermined database limit.


Overview________________Migration and Interworking

Data networks grow and evolve over time with the need for additional services and devices.Planning is necessary to minimize outage during network changes.

Migration

Migration refers to the systematic upgrade of a network from one release of the same network tothe next higher release of the same network. Depending on the existing configuration and theplanned configuration, this upgrade might require the replacement or the addition of hardwarecomponents and/or software.

Although all nodes in a network could be converted to the next release in a single cutover, it ismore likely that the migration is done in stages. All network releases provide extensive supportfor interworking with earlier releases and products; therefore there is no need to flash-cut an entirenetwork to the next release at once. Migration planning should consider the following network-wide issues:

Networks managed by StarKeeper II NMS may require a release upgrade ofStarKeeper II NMS to be performed before any network nodes can be upgraded.

Nodes, modules, configurations, or services used in the existing network that are notsupported in the new release, and their location, need special consideration.

Existing nodes that are not to be upgraded to the current software release should be located atthe edge of the network and not in an intermediate location.

Nodes that relay calls between other nodes should be upgraded to the current release.

Expansion of the existing network should occur with nodes running the new release.

An existing node upgrade depends on whether features included in the new release arerequired for the node.

Network user downtime and disruption should be planned around typical working hours.

Some features in the new release might not support interworking with earlier releases.

Blocking resources from some communities of users should be planned with localmanagement.

An area, an exchange, and a node name must be administered for each node to be upgraded.

Resolution of these issues determines when the migration to a new release could start.


Overview________________Interworking

Interworking refers to data communication in a network containing mixed node types. It allowscommunication between compatible endpoints on different types of nodes.

For example, a network containing primarily BNS-2000 nodes could be trunked to a BNS-2000VCS node with a supported trunk module, such as an SWT or Trunk-T1. Providing the endpointsare compatible (such as an asynchronous endpoint on a TY module in each node), the nodeswould interwork.

CLNS services on BNS-2000 nodes do not interwork with CONS on BNS-2000, BNS-2000VCS, Datakit II VCS, or BNS-1000 nodes.

In addition, Data Networking Products nodes also interwork with other Lucent Technologies’switches and communications systems such as the DEFINITY 75/85 Communications Systemand the 5ESS Switch.


________________Node

Node Types 2-3Limits 2-4Bus or Star Architecture 2-5Other Considerations 2-11

Critical Equipment Design 2-12Control Computer Configurations 2-12Power Configurations 2-16Switch Configurations 2-17

Shelf Design 2-17BNS-2000 VCS Configurations 2-17BNS-2000 Configurations 2-20Slot Numbering and Restrictions 2-25

Module Placement 2-31Series M1 Shelf Module Placement 2-31Series M2 Shelf Module Placement 2-32

Equipment Specifications and Compliances 2-33Physical Specifications 2-33Electrical Specifications 2-33Environmental Specifications 2-36Compliances 2-37

Site Preparation 2-39All Sites 2-39Customer Premises Sites 2-42CO Sites 2-48Peripheral Equipment 2-51


________________Node

This chapter explains how to plan the physical design of a node. It gives specifications for nodesand node-related equipment, including height and weight, electrical requirements, and capacities;and covers site planning and design issues. Other aspects of nodes are treated elsewhere, asfollows:

Routing is explained in the Routing chapter.

Node identifiers, such as the node name and its address, and other node issues are explained inthe Addressing and Database chapters.

Node console security is explained in the Security chapter.

Spare parts information is given in Appendix A.

In addition, the System Description contains a complete explanation of each supported node typeand the critical and redundant modules residing in the node. The Node Reference containsdetailed information on shelf/cabinet configurations and slot numbering.

Node Types

When planning a data switching network, the type of node is one of the primary considerations.The basic architecture of a node—its cabinets and the configurations they can assume, its circuitrydesign, and its inherent data transmission capabilities—determine which type of end user andshared services can be made available to the user community. The type of supported trunks thatlink the nodes in the network can also determine which node type is most appropriate; forexample, T3 trunks are supported only on BNS-2000 nodes.

Two basic node types are supported in the Data Networking Products family:

BNS-2000

BNS-2000 VCS

These node types have many common services and components, including many of the sameinterface modules. The primary difference is that the BNS-2000 node has a higher bandwidth andcan support more interfaces or trunks configured for transmission speeds of 1.5 Mbps or higher.This and other differences that affect node planning are described in the following sections.


Node________________Limits

BNS-2000 and BNS-2000 VCS node limitations are compared in the following table. The limitshown is the maximum number of the item that can be accommodated in one node. In order not toexceed backplane capacity, the combined load of all modules in use should not exceed the node’stotal backplane capacity.

TABLE 2-1. Node Capacities_ _________________________________________________________________________________

BNS-2000 VCS BNS-2000Item Limit Limit Remarks_ __________________________________________________________________________________ _________________________________________________________________________________

Shelves 8 8 BNS-2000 includes Series M1

and Series M2 Shelves.

BNS-2000 VCS includes

Series M1 Shelves only.________________________ ________________ ________________ ________________________

Series M1 8 7 BNS-2000 with only

1 Series M2 Shelf.

Series M2 — 6 BNS-2000 with up to

2 Series M1 Shelves._ _________________________________________________________________________________Data Switching Rate

Series M1 8 Mb 8 Mb virtual circuit switching

44,000 packets 44,000 packets 180-bit packets

per second per second________________________ ________________ ________________ ________________________

Series M2 — 200 Mb cell relay

460,000 segments 53-byte segments

per second_ _________________________________________________________________________________Interface modules and

trunk slots

BNS-2000 VCS

CCM Series M1 Control 8-12 — 12 with single CCM, single switch

Shelf 11 with single CCM, dual switch or

dual CCM, single switch

8 with dual CCM, dual switch,

internal tape

CCM Series M1 Port Shelf 14 —

ECPU Series M1 Control 5-8 — 5 with redundant Switch and

Shelf MRCM; 8 with ECPU in a

redundant cabinet.

ECPU Series M1 Port Shelf 14 —_ _________________________________________________________________________________


Node________________TABLE 2-1. Node Capacities (continued)_ ________________________________________________________________________________

BNS-2000 VCS BNS-2000Item Limit Limit Remarks_ _________________________________________________________________________________ ________________________________________________________________________________

BNS-2000

CCM Series M1 Control Shelf — 10–13 13 single CCM

— 12 dual CCM

— 10 dual CCM, internal tape

CCM Series M1 Port Shelf — 14

Series M2 Switch Shelf — 12

Series M2 Extension Shelf — 13

ECPU Series M1 Control Shelf — 7–8 7 with MRCM

ECPU Series M1 Redundant

Control Shelf — 8

ECPU Series M1 Port Shelf — 14_ ________________________________________________________________________________Concentrators 110 slots CCM node 97 slots CCM node Includes MPCs and SAMs.

104 slots ECPU node 91 slots ECPU node_ ________________________________________________________________________________Virtual Circuits 15,000 15,000 CONS environment_ ________________________________________________________________________________

Bus or Star Architecture

The shelves in each node type are interconnected to allow the various interface and trunk modulesto transfer information. The method of interconnecting the shelves is different for the two nodetypes:

The shelves in a BNS-2000 VCS node are interconnected via a common communication bus.

The shelves in a BNS-2000 node are interconnected via a star topology with the Series M2Switch Shelf at the center of the star.

Data transmission in a BNS-2000 VCS node and connection-oriented services on the BNS-2000node is based on virtual circuit switching. A virtual circuit is a full-duplex, end-to-endconnection between two communicating devices that depends on logical associations rather than adedicated physical pathway. Network resources and, in particular, bandwidth, are notpreallocated. Instead, bandwidth is used only during data transmission (Figure 2-1).


Node________________

Terminalor

Computer

Terminalor

Computer

InterfaceModule

InterfaceModule

2 5 3

SwitchModule

4Control Computer

16

FIGURE 2-1. A Virtual Circuit

BNS-2000 VCS Bus Architecture

BNS-2000 VCS nodes consist of one to eight Series M1 Shelves. These shelves are grouped intotwo functional types:

Series M1 Control Shelves — provide the switching and control computer function.

Series M1 Port shelves — provide slots for interface and trunk modules to gain access to theSwitch and Control Computer.

Control and port shelves are interconnected in a bus topology via the Clock and Repeater modulesin slot 15 of each cabinet. All network end devices, such as terminals and host computers, areconnected to specialized interface modules that are in turn connected, either directly or viaconcentration devices, to the 8 Mb backplane of its shelf.


Node________________

Switch

63

Repeater

Port Shelf 3

47

Port Shelf 2

31

Control orPort Shelf 1

15

ControlShelf 0

0

127

Clock

Port Shelf 7

111

Port Shelf 6

95

79

Port Shelf 5

Port Shelf 4

8-MbpsBus

Repeater

Repeater

Repeater

Repeater

Repeater

Repeater

8-MbpsBus

1

FIGURE 2-2. BNS-2000 VCS Bus Architecture Example


Node________________BNS-2000 Star Architecture

BNS-2000 nodes consist of Series M1 and Series M2 Shelves. These shelves are grouped intofour functional types:

Series M2 Switch Shelf is the hub of the node. It provides the 200 Mbps switching functionand interfaces to a total of seven additional Series M1 or M2 Shelves.

Series M2 Extension Shelves are port shelves that provide additional slots for Series M2interface and trunk modules to gain access to the Series M2 Switch Shelf 200 Mbpsbackplane.

Series M1 Control Shelves are 8 Mbps shelves that provide the control function for the node.

Series M1 Port Shelves provide additional slots for interface and trunk modules needingaccess to the 8 Mbps bus. Most BNS-2000 VCS trunk and interface modules can be used inthese Series M1 Shelves.

Data transmission on the 200 Mbps bus of a BNS-2000 node is based on cell relay, which is atechnique of multiplexing and switching 56 octets of fixed-length cells. BNS-2000 transmits thisdata without requiring any predefined connection, which results in its offering of a connectionlessnetwork service (CLNS) environment. The use of cell switching in addition to virtual circuitswitching enables BNS-2000 to handle many different types of traffic on a single network.

The BNS-2000 node uses a star architecture, with the Series M2 Switch Shelf as the hub asshown in the following figure. Each Series M2 Extension Shelf connects to a Series M2 SwitchShelf and shares one logical 200 Mbps backplane. Each Series M1 Shelf connects via a separate8 Mbps bus to the Series M2 Switch Shelf.

As the following two figures show, the star architecture of BNS-2000 nodes can assume variouscombinations of Series M1 and Series M2 Shelves. The minimum configuration consists of oneSeries M2 Switch Shelf and one Series M1 Control Shelf.

Refer to sections later in this chapter for more detailed explanations of BNS-2000 shelfconfigurations.


Node________________A standard shelf configuration, as shown in the following figure, could consist of the requiredSeries M2 Switch Shelf and Series M1 Control Shelf, another optional Series M1 Control Shelf,two optional Series M1 Port Shelves, and three optional Series M2 Extension Shelves for a totalof eight shelves maximum.

M1Control Shelf

M1Control Shelf

M1Port Shelf

M1Port Shelf

M2Switch Shelf

M2Extension Shelf

M2Extension Shelf

M2Extension Shelf

FIGURE 2-3. BNS-2000 Standard Star Architecture Example


Node________________An extended shelf configuration, as shown in the following figure, could consist of the requiredSeries M2 Switch Shelf and Series M1 Control Shelf, another optional Series M1 Control Shelf,and five optional Series M2 Extension Shelves.

M1Control Shelf

M1Control Shelf

M2Switch Shelf

M2Extension Shelf

M2Extension Shelf

M2Extension Shelf

M2Extension Shelf

M2Extension Shelf

FIGURE 2-4. BNS-2000 Extended Star Architecture Example


Node________________Other Considerations

Besides physical limits and architecture, the following considerations should be noted whenselecting the node type:

Only a BNS-2000 network offers CLNS and connection-oriented network service (CONS) viaits T3/E3 trunks.

In BNS-2000 networks containing Series M1 and Series M2 Shelves, Series M1 and SeriesM2 modules and I/O boards are not interchangeable. Series M1 module and I/O boards arebuilt to be inserted into the vertical shelves of Series M1 Shelves; Series M2 module and I/Oboards are built to be inserted into the horizontal shelves of Series M2 Shelves.

BNS-2000 nodes configured for the maximum Series M2 Extension Shelf configuration offive extension shelves must be numbered 1, 2, 3, 6, and 7. Shelves numbered 4 and 5 arereserved for a Series M1 Control Shelf and a Series M1 Control or Port Shelf.

BNS-2000 nodes configured for the maximum Series M2 Extension Shelf configuration offive extension shelves cannot have Group Address Modules (GARs) or any Series M2 Trunkmodule residing in Shelves 6 and 7. These modules can reside in Series M2 Shelvesnumbered 0, 1, 2, or 3 only.

In addition, these nodes must be carefully engineered to avoid backplane overload, which iscaused by bursty traffic and which manifests itself to the user as lost and garbled data.

In addition to the standard frame relay service offered with Frame Relay Modules (FRMs),BNS-2000 networks offer frame relay service via FRM-M2s, which reside in Series M2Shelves.

BNS-2000 VCS Series M1 Shelves can easily be upgraded to BNS-2000 Series M1 Shelvesby replacing the Repeater module with a Clock/Trunk/Repeater Module (CTRM). With theaddition of a single Series M2 Shelf, a Cabinet Interface Module (CIM), and a CTRM, aBNS-2000 VCS node can be converted to a BNS-2000 node.


Node________________Critical Equipment Design

The equipment critical to node functioning is also critical to node availability and proper networkfunctioning; therefore, the various configurations of critical equipment available should becarefully considered and well planned.

Control Computer Configurations

Two types of Control Computer configurations are supported. Each type includes its ownimplementation of components similar in function:

The Control Computer Module (CCM) configuration incorporates the functions of a CPU, a dualSmall Computer Systems Interface (SCSI) and controller, a disk drive, and one of twoinput/output (I/O) distribution boards:

— the simplex I/O board

— the Maintenance and Redundancy Controller I/O (MRCIO) board

These functions reside on one module and I/O board set that is housed in a Series M1 Shelf.In addition, each node can have any one of the following tape drive configurations:

— one external tape drive, which is an external device that draws separate AC power

— one internal tape drive, which consists of a board set that uses two slots in a Series M1Shelf

— no tape drive—StarKeeper II NMS is used for software download and data storage,retrieval, and archiving


Node________________The ECPU configuration provides the functions of a CPU, a SCSI and controller (SCSI/DKI),a Maintenance and Redundancy Control Module (MRCM), and a disk and tape drivesubsystem. These functions reside on separate module and I/O board sets that are housed in aSeries M1 Shelf.

NOTE: Any configuration that requires remote maintenance and/or the automatic recovery ofthe Control Computer requires an MRCIO or an MRCM. In a CCM configuration, theMRCIO is used as the I/O board for the CCM module board. In an ECPUconfiguration, the MRCM consists of the MRCM module board and the MRCM I/Oboard. Since the MRCIO in CCM configurations supports the same functions as theMRCM in ECPU configurations, the function of both components is hereafter referredto as the MRC function.

Each type of Control Computer configuration supports a single and dual arrangement ofcomponents:

A single configuration of the Control Computer and its critical modules and peripheralssupports manual recovery only. The optional MRC function provides the capability of remotemaintenance only.

A dual configuration of the Control Computer and its critical modules and peripherals supportsa higher level of availability, automatic Control Computer recovery, and remote maintenance.The MRC function is required. Dual configurations must consist of like controllers: twoCCMs or two ECPUs; controller types cannot be mixed.


Node________________The following table summarizes possible single and dual CCM configurations. The CCM moduleboard and its MRCIO or simplex I/O board can be installed in any Series M1 Shelf, making it acontrol shelf. The internal tape drive can be installed in any Series M1 Control Shelf. It uses twoslots. The tape drive can also be an external device. The external tape drive measures 236mm by155mm by 69mm, or 9-5/16 inches by 6-1/8 inches by 2-3/4 inches.

CCM configurations without a tape are those that rely on StarKeeper II NMS for data storage,retrieval, and archiving.

TABLE 2-2. Supported CCM Single and Dual Configurations

_ ______________________________________________________________________Series M1 Shelf External

Node-Resident Boards Device_ ____________________________________________________Internal

Tape External

Configuration CCM Simplex I/O MRCIO (TN2233) Tape

Type (TN2235) (CTS2) (CTS1) (CSD9) (ED3P325-30,G407)_ _______________________________________________________________________ ______________________________________________________________________Single √ √_ ______________________________________________________________________Single with MRC √ √_ ______________________________________________________________________

√ √ √_ ____________________________________________________Single with Tape √ √ √_ ______________________________________________________________________

√ √ √_ ____________________________________________________Single with MRC & Tape √ √ √_ _______________________________________________________________________ ______________________________________________________________________Dual with MRC √√ √ √_ ______________________________________________________________________

√√ √ √ √_ ____________________________________________________Dual with MRC & Tape √√ √ √ √_ ______________________________________________________________________


Node________________The following table summarizes possible single and dual ECPU configurations. For a singleconfiguration, the Control Computer, Disk/Tape Subsystem, and the MRCM module and I/Oboards can be installed in any Series M1 Control Shelf. For a dual configuration, one ControlComputer and Disk/Tape Subsystem must reside in a BNS-2000 Series M1 Control Shelf and thesecond interconnected Control Computer and Disk/Tape Subsystem must reside in the next higherSeries M1 Control Shelf. The MRCM, which ensures that one Control Computer is active andone is standby, is required in the lower number shelf/cabinet.

TABLE 2-3. Supported ECPU Single and Dual Configurations

_ _______________________________________________________________Series M1 Shelf Node-Resident Boards_ __________________________________________________

ECPU SCSI/DKI MRCM Disk Tape

Configuration (MC1D138A1) (UN635B) (TN2109C) (TN2175B) (TN2097)

Type (AWJ15) (ASP4B) (AWJ16B) (AWJ12) (ASP8)_ ________________________________________________________________ _______________________________________________________________Single √ √ √ √_ _______________________________________________________________Single with MRC √ √ √ √ √_ ________________________________________________________________ _______________________________________________________________Dual with MRC √√ √√ √ √√ √√_ _______________________________________________________________

A Control Computer failure in a single configuration affects some node services, such as settingup and taking down calls, but does not affect established calls. The time-to-repair (TTR), ordowntime, depends on the time needed for the servicing organization to respond to the servicecall, diagnose the failure, obtain spare parts, replace any failed modules in the Control Computer,and reboot and restore the node to service.

A Control Computer failure in a dual configuration has minimal impact on services. Because thenode can automatically transfer control from the failed Control Computer to the redundantControl Computer, downtime is reduced to the time required to reboot. With a spare ControlComputer, the mean time between failures (MTBF) is increased to about 25 months for a four-cabinet/shelf node or a overall node availability of 99.99%.

The MRC function provides the automatic Control Computer recovery function. It detects afailure of the active, on-line Control Computer, automatically switches control to the standbyunit, and reboots the system. Failure detection generally occurs within a few seconds of thefailure. During the period of failure detection, recovery, and reboot, calls are not set up or takendown. However, calls established through the node are maintained. The time needed to reboot istypically two minutes. After rebooting, the Control Computer must audit the Switch module andrecover active calls. The time required for this step varies from one to seven minutes dependingon the configuration size.


Node________________The MRC function can also be used to assist in remote maintenance for both single and dualControl Computer configurations. It provides the ability to recover manually from a transientfailure in the Control Computer without being present on-site. Remote maintenance can beperformed via a remote node console or through StarKeeper II NMS.

The following table summarizes the functions and/or features each Control Computerconfiguration supports.

TABLE 2-4. Control Computer Configurations Features/Functions Supported

_ ____________________________________________________________CCM ECPU Function/Feature

Configuration Configuration Supported_ _____________________________________________________________ ____________________________________________________________√ √ Resides in Series M1 Control Shelf._ ____________________________________________________________√ Functions housed on one board set;

occupies minimal node slots._ ____________________________________________________________√ Functions housed on multiple board sets;

occupies several node slots._ ____________________________________________________________√ Redundancy achieved in same shelf/cabinet._ ____________________________________________________________√ √ Redundancy achieved in two shelves/cabinets._ ____________________________________________________________√ Cabling complexity reduced._ ____________________________________________________________√ √ High performance._ ____________________________________________________________√ √ High availability._ ____________________________________________________________√ Faster call set-up and processing._ ____________________________________________________________√ One optional internal/external tape drive._ ____________________________________________________________

√ One required internal tape drive._ ____________________________________________________________

Power Configurations

Control Computer availability can be improved with redundant power supplies. Series M1Shelves are equipped with three power supplies, and Series M2 Shelves are equipped with fourpower supplies. In both shelves, one power supply is redundant. (However, the third powersupply in a Series M1 Shelf prevents use of the first addressable slot in each cabinet where it isinstalled.)

By limiting cabinet/shelf power consumption to its maximum recommended load (Tables 2-10,2-11, 4-6, and 5-47) the shelf can operate continuously despite the failure of one power supply.For example, each power supply in a Series M1 Shelf supplies 40 amps at +5 VDC. By limitingthe overall power consumption to no more than 80 amps (at +5 VDC), the shelf can continue tooperate if one power supply fails.


Node________________Switch Configurations

Node availability can be further improved through the use of a redundant Switch module. In aredundant configuration, the active Switch is backed up by a standby Switch. If the active Switchfails, the Control Computer can automatically switch over to the standby Switch.

The MTBF for the BNS-2000 VCS Switch is approximately 7.6 years. Using a conservativeestimate of two hours of mean time to repair (MTTR), the availability of a single Switch is99.997%. Placing a redundant Switch in the BNS-2000 VCS node increases Switch availabilityto 99.999%. The BNS-2000 node is always equipped with a redundant Switch.

Shelf Design

Various shelf configurations are possible. The following sections explain the number of shelvesallowed for different types of configurations, the arrangements of the shelves, and slot numberingand restrictions.

BNS-2000 VCS Configurations

A BNS-2000 VCS node must have one Series M1 Shelf and can have a maximum configurationof eight Series M1 Shelves. Of these shelves, one shelf must be a control shelf and the remainingshelves can be port shelves.

For redundant ECPU configurations, one port shelf is replaced by a second control shelf.

The following table shows the allowable combinations of shelves in a node, and the followingfigure shows the maximum configuration of shelves in a node.

TABLE 2-5. BNS-2000 VCS Series M1 Shelf Combinations in a Node

_ ______________________________Number of Number of Port

Control Shelves Shelves Allowed_ _______________________________ ______________________________1 0–7_ ______________________________2 0–6_ ______________________________


Node________________

PortShelf

PortShelf

Port orRedundantControlShelf

ControlShelf

PortShelves

Base Power Units

FIGURE 2-5. BNS-2000 VCS Maximum Node Shelf Arrangement


Node________________For a single CCM configuration, the Series M1 Control Shelf must contain the CCM and its I/Oboard, along with a Switch and a Clock/Repeater. The optional tape drive can reside in the SeriesM1 Control Shelf or it can be an external device that has separate AC power.

For dual CCM configurations, two CCMs, the Simplex I/O, the MRCIO, the Switch, and theClock/Repeater can reside in the same Series M1 Control Shelf or in two separate Series M1Control Shelves. The tape drive can reside in one of the Series M1 Control Shelves; or the tapedrive can be an external device that has separate AC power.

For an ECPU configuration, a Series M1 Control Shelf contains the following modules, all ofwhich must reside in the same physical Series M1 Control Shelf: a Control Computer including aSwitch, a Clock or a Repeater module; a Disk/Tape Subsystem; and an MRCM when a redundantControl Computer is used. The redundant Series M1 Control Shelf does not contain a Switch oran MRCM.

The Series M1 Port Shelf differs from the Series M1 Control Shelf only in the type of modulesinstalled in its slots. The Series M1 Port Shelf contains power supplies, interface and trunkmodules, and a Repeater module in the highest numbered slot, except in the last Series M1 PortShelf, which contains a Clock module in the highest numbered slot.

Environments

For customer premises environments, the Series M1 shelves are stacked on top of each other witha maximum of four Series M1 shelves per stack, two stacks per node.

A Base Power Unit (Figure 2-4) supplies power options such as alternating current (AC)distribution. The Base Power Unit is used only in AC powered installations, not in −48 directcurrent (DC) central office (CO) installations. The housing serves as the base for a stack of SeriesM1 shelves. One Base Power Unit is required per four Series M1 shelves. Refer to the NodeReference for more details on Base Power Unit options and power components.

BNS-2000 VCS nodes in a CO environment require Series M1 shelves to be stacked and wired ina CO frame. One CO frame is required per four Series M1 shelves. (See Figure 2-15.)Additional components, such as an optional Alarm Relay Unit (ARU), are included. The ARU ismounted in the CO frame and connects to the Series M1 Control Shelf.

Numbering

In BNS-2000 VCS nodes, the Series M1 shelf designated to be the control shelf is shelf number0. Seven additional Series M1 shelves (numbered 1 through 7), known as port shelves, can beadded to the configuration.

If the node contains a dual ECPU configuration, shelf 1 is used as the second control shelf. In adual CCM configuration, shelf 1 may optionally be used as the second control shelf. In all cases,the Series M1 Control Shelves must be vertically adjacent in the same stack because of the lengthof the cables connecting the Control Computer modules and the MRCM/MRCIO.


Node________________BNS-2000 Configurations

The minimum configuration for a BNS-2000 node consists of one Series M2 Switch Shelf andone Series M1 Control Shelf. Up to five Series M2 Extension Shelves or up to seven Series M1Shelves (including Control Shelves) can be added. However, the total number of shelves in anode is limited to eight.

BNS-2000 node configurations with up to three Series M2 Extension Shelves use the standardswitch complex along with multi-coax intershelf cabling. When the standard configuration ofthree extension shelves is upgraded to the maximum configuration of five Series M2 ExtensionShelves, the extended switch complex and high density intershelf cabling are required.

NOTE: BNS-2000 node configurations that include the Stratum 4 Clock upgrade also requirethe extended switch complex.

The following table shows the allowable combinations of Series M1 and Series M2 Shelves in anode, and the following two figures show the maximum configurations for Series M2 and SeriesM1 Shelves in a node.

TABLE 2-6. Series M1 and Series M2 Shelf Combinations in a BNS-2000 Node

_ ____________________________________________________________Series M2 Shelves Series M1 Shelves_ ____________________________________________________________

Number of Number of Number of PortSwitch Shelf

Extension Shelves Control Shelves Shelves Allowed_ _____________________________________________________________ ____________________________________________________________1 0–6_ ______________________________

1 02 0–5_ ____________________________________________________________1 0–5_ ______________________________

1 12 0–4_ ____________________________________________________________1 0–4_ ______________________________

1 22 0–3_ ____________________________________________________________1 0–3_ ______________________________

1 32 0–2_ ____________________________________________________________1 0–2_ ______________________________

1 42 0–1_ ____________________________________________________________1 0–1_ ______________________________

1 52 0_ ____________________________________________________________


Node________________M2 Extension

Shelf 3

605958

48A

M2 ExtensionShelf 2

4443

32A

M2 ExtensionShelf 1

2827

18A

112 M1 PortShelf 7

127

CTRM

96 M1 PortShelf 6

111

CTRM

80 M1 ControlShelf 5

95

CTRM

64 79

CTRM

CC

CC

121110987654321BA

CIMCIMCIMCIM

Switch*Switch*

M2 SwitchShelf 0

3 2 1 CNA1 (Rear View)

Fiber

Multi-coaxial

M1 ControlShelf 4

* Either the CTG13 or CMA1 switch complex can be used.

FIGURE 2-6. Maximum Configuration of Series M1 Shelves in a BNS-2000 Node


Node________________M2 Extension

Shelf 3

605958

48A

M2 ExtensionShelf 2

4443

32A

M2 ExtensionShelf 1

2827

18A

80 M1 ControlShelf 5

95

CTRM

64 79

CTRM

CC

CC

121110987654321BA

CIMCIM

CTG13 SwitchCTG13 Switch

M2 SwitchShelf 0

CNA7 (Rear View)

Fiber

Multi-coaxial

M2 ExtensionShelf 6

108107106

9796

M2 ExtensionShelf 7

124123122

113112

M1 ControlShelf 4

FIGURE 2-7. Maximum Configuration of Series M2 Shelves in a BNS-2000 Node


Node________________Environments

For customer premises environments, the shelves are stacked on top of each other with amaximum of four shelves per stack, two stacks per node.

A Base Power Unit (Figures 2-11 and 2-12) supplies power options such as AC distribution. TheBase Power Unit is used only in AC powered installations, not in −48 volt DC CO installations.The housing serves as the base for a stack of shelves. One Base Power Unit is required per fourshelves. Refer to the Node Reference for more details on Base Power Unit options and powercomponents.

BNS-2000 nodes in a CO environment require node shelves to be stacked and wired in a COframe. One CO frame is required per four shelves. (See Figure 2-15.) Additional components,such as the Alarm Relay Unit (ARU), are included. The ARU is mounted on the top of the COframe and connects to the Control Computer.

If the node contains a dual ECPU configuration or a dual CCM configuration in which the CCMsdo not reside on the same shelf, the Series M1 Control Shelves must be vertically adjacent in thesame stack because of the length of the cables connecting the Control Computer modules in thetwo shelves.

For BNS-2000 nodes with more than four shelves, shelves should be stacked in increasingnumerical order: shelves 0, 1, 2, and 3 in the first stack; shelves 4, 5, 6, and 7 in the secondstack.

For BNS-2000 nodes with four or fewer shelves, put all shelves in one stack.

Series M1 Shelves should always use shelf numbers 4 and 5 first.


Node________________Numbering

Each BNS-2000 node shelf is assigned a logical number, which is used to determine its physicalposition in the stacking arrangement.

The BNS-2000 Series M2 Switch Shelf is always assigned shelf number 0, regardless of howmany Series M2 Extension Shelves are added to the configuration.

A BNS-2000 Series M1 Control Shelf should be assigned to shelf number 4. If used in dualCCM/ECPU configurations, a redundant Series M1 Control Shelf should be assigned to shelfnumber 5, and the MRCIO/MRCM should be located in shelf number 4.

Each Series M1 Shelf connects to a Series M2 Switch Shelf via a CIM-CTRM link. TheClock/Trunk/Repeater Module (CTRM) in the Series M1 Shelf is connected via a fiber link to aCabinet Interface Module (CIM) in the Series M2 Switch Shelf. The CIM can go into any slotfrom 1 to 7 in the Switch Shelf. Each Series M1 Shelf is numbered according to the slot numberof the CIM connecting it to the Switch Shelf.

Configurations with Three Series M2 Extension Shelves. For BNS-2000 shelfconfigurations that have three Series M2 Extension Shelves, the shelf number is derived from theplug position of the interface cable in the CNA1. The CNA1 I/O board is located behind theCMA1 Switch module in the Series M2 Extension Shelf. It has three connectors for multi-coaxcables to Series M2 Extension Shelves, numbered from 1 to 3. Each Extension Shelf is numberedaccording to the connector it uses on the CNA1.

A potential conflict exists between Series M2 Extension Shelves, which can use shelf numbers 1to 3 only, and Series M1 Shelves, which can use any shelf number from 1 to 7. Whenever anExtension Shelf is plugged into the Switch Shelf and is using a shelf number from 1 to 3, thatnumber cannot be used for a Series M1 Shelf; that is, if an Extension Shelf is connected toconnector 1 of the CNA1, a CIM cannot be put in slot 1 of the Switch Shelf. That slot can beused for an interface module or trunk module, but not for a CIM.

Configurations with Five Series M2 Extension Shelves. For BNS-2000 shelfconfigurations that have the maximum of five Series M2 Extension Shelves, the shelf number isderived from the plug position of the interface cable on the CNA7 Extended Cable/Clock and RIBStatus I/O board. The CNA7 I/O board is located behind the CTG13 Extended Switch module inthe Series M2 Switch Shelf. The CNA7 has five connectors for high density intershelf cables thatconnect to Series M2 Extension Shelves, numbered 1, 2, 3, 6, and 7. Each Extension Shelf isnumbered according to the connector it uses on the CNA7.

A potential conflict exists between Series M2 Extension Shelves, which can use shelf numbers 1,2, 3, 6, and 7 only, and Series M1 Shelves, which can use any shelf number from 1 to 7.Whenever an Extension Shelf is plugged into the Switch Shelf and is using shelf number, 1, 2, 3,6, or 7, that number cannot be used for a Series M1 Shelf; that is, if an Extension Shelf isconnected to connector 1 of the CNA7, a CIM cannot be put in slot 1 of the Switch Shelf. Thatslot can be used for an interface module or trunk module, but not for a CIM.


Node________________Slot Numbering and Restrictions

All slots in any Series M2 or M1 Shelf are viewed as attachments to the node backplane. Slots inSeries M2 Shelves are horizontal; slots in Series M1 Shelves are vertical. Regardless of thephysical orientation of a slot, the slot number of a module corresponds to the module address of amodule, which depends on its addressable location in a shelf and its number.

BNS-2000 VCS Slot Numbering

With BNS-2000 VCS nodes, the slot numbers of the Series M1 Control Shelf range from 0through 15; and the 16 addressable slot numbers in the seven additional Series M1 Port Shelvesdepend on the shelf number. See the following table.

TABLE 2-7. Series M1 Shelf Number and Module Address Correspondences

_ _________________________Series M1 Shelf Module

Number Addresses_ __________________________ _________________________0 (Control) 1-15_ _________________________

1 (Control or Port) 16-31_ _________________________2 (Port) 32-47_ _________________________3 (Port) 48-63_ _________________________4 (Port) 64-79_ _________________________5 (Port) 80-95_ _________________________6 (Port) 96-111_ _________________________7 (Port) 112-127_ _________________________

Power Supplies. In each control and port shelf configured, the first two slots are reserved forthe two required power supplies; these non-addressable slots are not numbered. The nextaddressable slot is reserved for the redundant power supply. Since this power supply is an optionin shelves that do not house the disk and tape drives, it can be removed and the slot can be used asaddressable slot 0. However, configurations that use the redundant power supply arerecommended; configurations that do NOT use the redundant power supply are NOTrecommended.

Single Control Computer Configurations. For a single CCM configuration in a Series M1Control Shelf, the recommended location for the CCM is shelf 0, slot 14.

For a single ECPU configuration in a Series M1 Control Shelf, the recommended location for theControl Computer is shelf 0. The SCSI/DKI module must always be located in addressable slots14, 30, 46, 62, 78, 94, 110 or 126. If the MRCM is present, the Control Computer must beinstalled in shelf 0 or 1 because the MRCM must be cabled to the Repeater in shelf 1.


Node________________Dual Control Computer Configurations. For dual CCM configurations in a Series M1Control Shelf, the recommended location for the CCM is shelf 0, slots 13 and 14 or shelf 0, slot14 and shelf 1, slot 30. The CCM located in the lower numbered slot is CC0.

For dual ECPU configurations, one Control Computer must be located in shelf 0 because ofMRCM restrictions. Consequently, the ECPU Control Computers must be located in shelf 0 andshelf 1.

Switch. The Switch must be located in the lowest addressable slot number; slot 1 for a singleSwitch and slots 1 and 2 for dual Switches.

Clock and Repeater Modules. The highest addressable slot in each port shelf is reserved forthe Repeater module or, in the highest address of the node, the Clock module. The remainingslots accommodate any interface modules that can be installed in the node.

If port shelves are added to the control shelf, the Clock must be interchanged with the Repeater inthe highest numbered shelf. The Clock should always go in the highest addressable slot in thehighest numbered shelf because the Control Computer does not activate any module for servicethat is placed above the Clock. In a multishelf configuration, therefore, the Clock must be in thehighest port shelf.

Each Series M1 Shelf, except the one containing the Clock (which has its own internal repeater),contains a Repeater. The Repeater is installed in the highest addressable slot in each shelf. TheRepeater is a critical module; if it fails, the node fails.

Tape Drive Configuration. For the CCM with an internal tape drive, the recommended slotsare the two slots immediately to the left of the first CCM.

Remaining Modules. The slots not occupied by the power supplies, the Control Computerand its components, and the Clock and Repeater are available for Series M1 trunk and interfacemodules. Some modules contain two circuit boards. The leftmost board in these double-boardmodules (the one containing the status LEDs and switches) must be installed in the leftmost slotin a slot pair.


Node________________BNS-2000 Overall Slot Numbering

Each Series M1 Shelf and Series M2 Shelf has a label attached at installation for identifying themodule addresses. To find the module address of a module from its shelf number and slot, usethe following equation:

<module address> = (16 × <shelf number>) + <slot number>

Where: shelf number and slot number are the following:

<shelf number> 0 is reserved for the Series M2 Switch Shelf.

1, 2, 3, 6, or 7 can be assigned to a Series M2 Extension Shelf.

1 to 7 can be assigned to a Series M1 Control Shelf or Port Shelf.

<slot number> Ranges from 1 to 12 are used for the Series M2 Switch Shelf.

Ranges from 0 to 12 are used for an Series M2 Extension Shelf.

Ranges from 0 to 15 are used for a Series M1 Control Shelf or Series M1 Port Shelf;

however, slot 0 is used by the redundant power supply.

Example: The TY in slot 7 of shelf 4 = (4 × 16) + 7 = 71

To keep module addresses consistent for both Series M1 and Series M2 Shelves, moduleaddresses 29 to 31, 45 to 47, 61 to 63, 109 to 111, and 125 to 127 are not used in Series M2Shelves. Therefore, the first address in each shelf is always a multiple of 16. The following tableprovides the correspondence between the shelf number and the module address.

TABLE 2-8. Series M1 and Series M2 Shelf Number and Module AddressCorrespondences

_ ___________________________________________Shelf Series M1 Series M2

Number Module Addresses Module Addresses_ ____________________________________________ ___________________________________________0 A, B, 1-12

(Switch Shelf)_ ___________________________________________1 16-31 16-28_ ___________________________________________2 32-47 32-44_ ___________________________________________3 48-63 48-60_ ___________________________________________4 64-79_ ___________________________________________5 80-95_ ___________________________________________6 96-111 96-108_ ___________________________________________7 112-127 112-124_ ___________________________________________


Node________________Series M2 Shelf Slot Numbering

Both the Series M2 Switch Shelf and the Series M2 Extension Shelf contain 14 horizontal slotsthat can house Series M2 modules.

Slots 0/A and 0/B in a Series M2 Switch Shelf. Slots 0/A and 0/B, which are the bottom twoslots in a Series M2 Switch Shelf, are reserved for switching and Stratum 4 clocking. The SwitchShelf requires two switch modules—one is an active switch; the other is a standby that mirrorsthe memory of the active switch.

Configurations with three Series M2 Extension Shelves use the standard CMA1 Switchcomplex and the Stratum 4 (SSM4) Clock.

The primary CMA1 Switch, which is located in slot 0/A, uses the CNA1 IntershelfCable/Clock (ICC) I/O board. The redundant CMA1 Switch, which is located in slot 0/B infront of the Stratum 4 Clock (SSM4), uses the CMC3 I/O board.

On nodes providing SMDS or FRM-M2 services, the SSM4 uses the primary or secondarytiming reference to synchronize the signal it produces and to send it on to the CNA1 fordistribution to the Series M2 Shelves in the node.

The back of the lowest slot (slot A) in each Series M2 Extension Shelf can be occupied onlyby the CNA2 I/O board; therefore the bottom slot A of the Extension Shelf must remainempty and 13 slots remain available for interface modules.

Configurations with five Series M2 Extension Shelves use the CTG13 Extended SwitchComplex, which has an integrated Stratum 4 (STR4) clocking and synchronization function.

The primary CTG13 Extended Switch is located in slot 0/A and the redundant CTG13Extended Switch is located in slot 0/B. Both use the CNA7 Extended Cable/Clock and RIBStatus I/O Board, which is a double board module. The CNA7 supports connections for theSeries M2 Extension Shelves and handles the connections for Stratum clock references. It hastwo connectors for reference input boards, or RIBs (CUW1s), which support T1, E1, or64KCC references.

The back of the lowest slot (slot A) in each Series M2 Extension Shelf can be occupied onlyby the CNA8 I/O board; therefore the bottom slot A of the Extension Shelf must remainempty and 13 slots remain available for interface modules.

Slots 1 to 7 in a Series M2 Switch Shelf. In the Series M2 Switch Shelf, addressable slots 1to 7 can contain either CIM or Series M2 interface modules. At least one slot in this range mustbe used for a CIM connecting to the one required Series M1 Control Shelf, which should reside inslot 4. CIMs connecting to Series M1 Control Shelves or Port Shelves via fiber connections canuse any slot in this range. Slots 1, 2, 3, 6, and 7 should be reserved for future Series M2Extension Shelves, but can be used for Series M1 Port Shelves if additional Extension Shelvesare not required.

Slots 8 to 12 in a Series M2 Switch Shelf. Slots 8 to 12 in the Series M2 Switch Shelf cancontain any Series M2 interface or trunk module.

Slots 1 to 12 in a Series M2 Extension Shelf. Slots 1 to 12 in the Series M2 ExtensionShelves that are numbered 1, 2, or 3 can contain any Series M2 interface or trunk modules.


Node________________Slots 1 to 12 in the Series M2 Extension Shelves that are numbered 6 or 7 cannot contain anySeries M2 GAR or M2 trunk module.

Series M1 Shelf Slot Numbering

The slot numbers of the Series M1 Control Shelf range from 0 through 15; and the 16 addressableslot numbers of up to seven additional Series M1 Port Shelves also correspond to modular cabinetslot numbers shown in Table 2-7.

Power Supplies. In each Series M1 Control and Port Shelf configured, the first two slots arereserved for the two required power supplies; these non-addressable slots are not numbered. Thenext addressable slot is reserved for the redundant power supply. Since this power supply is anoption in cabinets that do not house the disk and tape drives, it can be removed and the slot can beused as addressable slot 0. However, configurations that use the redundant power supply arerecommended; configurations without the redundant power supply are NOT recommended.

Single Control Computer Configurations. For a single CCM configuration in a Series M1Control Shelf, the recommended location for the CCM is shelf 4, slot 14, which allows shelfnumber 2 and 3 to be either a Series M1 or Series M2 Shelf.

For a single ECPU configuration in a Series M1 Control Shelf, the recommended location for theControl Computer is shelf 4 to allow shelf number 2 and 3 to be either Series M1 Port or SeriesM2 Extension Shelves. In all cases, the ECPU module must reside in physical slot 13 and theSCSI/DKI in physical slot 14 of the Series M1 Control Shelf. If the MRCM is present, it must beinstalled in the Control Computer shelf because it must be cabled to the CTRM in the ControlComputer cabinet.

Dual Control Computer Configurations. For dual CCM configurations in a Series M1Control Shelf, the recommended location for the CCM is shelf 4, slots 13 and 14 or shelf 4, slot14 and shelf 5, slot 14. If the MRC function is to be used, the MRCIO must reside behind thelower numbered CCM.

For dual ECPU configurations, the second Series M1 Control Shelf must be physically adjacentin the same cabinet stack to the first Series M1 Control Shelf because of interconnecting cablingrestrictions. Consequently, dual Control Computers should be located in shelf 4 and shelf 5 in thesame cabinet stack. The MRCM must be installed in the lower numbered Control Computer shelfand it must be cabled to the CTRM in the Control Computer cabinet.

CTRM. The highest addressable slot in each Series M1 Control or Port Shelf is reserved for theCTRM. The remaining slots accommodate any interface modules that can be installed in thenode.

Remaining Modules. The slots not occupied by the power supplies, the Control Computerand its components, and the CTRM are available for Series M1 trunk and interface modules.Some modules contain two circuit boards. The leftmost board in these double-board modules (theone containing the status LEDs and switches) must be installed in the leftmost slot in a slot pair.


Node________________BNS-2000 Shelf/Module Relationship

The total number of Series M1 and Series M2 modules in a node depends on the nodeconfiguration—that is, how many of each type of shelf is configured. The following table showsthe overall relationship of the number of shelves in a node to the number of modules of each type.Note the following:

The maximum number of Series M2 modules in the Switch Shelf is reduced by one for eachPort or Control Shelf added.

The maximum number of Series M1 modules depends on the maximum number of PortShelves and the type of Control Computer configuration used. Calculations given are basedon a configuration with three power supplies and a CTRM in each Series M1 Shelf.

Each single ECPU Control Shelf configuration provides 8 slots; dual ECPU Control Shelfconfigurations provide 7 slots in the shelf containing the MRCM and 8 slots in the redundantshelf; each Port Shelf provides 14 slots.

A CCM Control Shelf has 13 slots for Series M1 modules if one CCM is used. Since a dualCCM configuration can have both CCMs on the same shelf or both CCMs on differentshelves, 12 slots are available on the Series M1 Control Shelf if two CCMs are configured onthe same shelf or 13 if each CCM is configured on a different shelf. The figures shown in theControl Shelf column in the following table assume that one CCM is installed per ControlShelf. The figures shown in the CCM Maximum Modules column assume that an externaltape device is configured. If an internal tape drive is configured, subtract two from eachnumber in the CCM Maximum Modules column.


Node________________TABLE 2-9. Number of User Interface Modules in a Node

_ __________________________________________________________________________Series M2 Shelves Series M1 Shelves_ __________________________________________________________________________

Number of Number of Number of ECPU CCMSwitch Extension Maximum Control Port Maximum MaximumShelf Shelves Modules* Shelves Shelves Modules* Modules*_ ___________________________________________________________________________ __________________________________________________________________________

1 0 11 1 0–6 92 97_ _______________________________________________________10 2 0–5 85 96_ __________________________________________________________________________

1 1 24 1 0–5 78 83_ _______________________________________________________23 2 0–4 71 82_ __________________________________________________________________________

1 2 37 1 0–4 64 69_ _______________________________________________________36 2 0–3 57 68_ __________________________________________________________________________

1 3 50 1 0–3 50 55_ _______________________________________________________49 2 0–2 43 54_ __________________________________________________________________________

1 4 63 1 0–2 36 41_ _______________________________________________________62 2 0–1 29 40_ __________________________________________________________________________

1 5 76 1 0–1 22 27_ _______________________________________________________

75

2

0

15

26_ __________________________________________________________________________* Depicts only the maximum configurable modules for the node configuration; does not imply supported maximum capacity._ __________________________________________________________________________

Module Placement

Series M1 modules can only reside in Series M1 Shelves or MPCs. Series M2 modules can onlyreside in Series M2 Shelves. Since the slots of each shelf are of different sizes—Series M1Shelves and MPCs are vertical; Series M2 Shelves are horizontal—a module does not fit into theslots of both shelves.

Series M1 Shelf Module Placement

When placing modules in Series M1 Shelves, consider what factor below is most important andfollow the recommendations that best apply. In some cases, module backplane bus contentionmay be an issue.

For BNS-2000 VCS nodes whose backplane utilization is more than 70%, place moduleswhose traffic is considered high priority into the highest numbered shelves. The highestpriority is given to modules in the highest numbered shelf.

For BNS-2000 nodes, module contention in different shelves is not an issue because shelvesare serviced in a round-robin fashion, and no shelf has higher priority than any other shelf.


Node________________For Series M1 Shelves, place modules whose traffic is considered high priority in slots withthe highest module addresses in each shelf. The winner of bus contention for packet transportis determined by module number; the module with a higher address has higher priority thanany module on that shelf with a lower address. Priority is an issue only when the backplaneusage is above 70%. Apply this recommendation to virtual circuits where delay through thenode or buffer space is an issue.

Terminating endpoints (call destinations, such as trunk and multiplexed host computerinterface modules) should be placed into lower-numbered addresses, while originatingendpoints (call originators, such as terminals) should be placed into higher-numberedaddresses. During a cold boot of the node, modules are downloaded and activated insequence, starting with the module residing in the lowest module address and ending with themodule residing in the highest module address. Activate receiving modules before originatingmodules to avoid the possibility of poor route selection and other anomalous behavior.

Place interactive (echoplexing) modules in relatively high priority slots to provide theminimum echo delay.

Place streaming data modules, such as host servers, trunks, and LAN bridges, in relatively lowpriority slots to use the backplane capacity left idle from the modules with interactive traffic.

The total traffic for a Series M1 Shelf in a BNS-2000 node must be within the shelf backplanebandwidth limit of 8 Mbps. If traffic is expected to approach T1 capacity, no more than threeinterface modules operating at T1 speed should be configured on any given Series M1 Shelf.However, if traffic is bursty, it is unlikely that all interfaces will be active at once; so use thebursty nature of the traffic to configure more capacity than the backplane maximum.

Series M2 Shelf Module Placement

Two-board SMDS modules, such as the AI-T3P and Trunk-T3I, must be installed in consecutiveslots in Series M2 Shelves. The board designated to carry ingress traffic must be located in thenext higher numbered slot.

BNS-2000 nodes configured for the maximum Series M2 Extension Shelf configuration of fiveextension shelves cannot have GAR or any Series M2 Trunk module residing in Shelves 6 and 7.These modules can reside in Series M2 Extension Shelves numbered 0, 1, 2, or 3 only.

In addition, these nodes must be carefully engineered to avoid backplane overload, which iscaused by bursty traffic and which manifests itself to the user as lost and garbled data.


Node________________Equipment Specifications and Compliances

When planning a network and each node site, the size and weight of each piece of equipmentmust be considered before the initial installation and for long-term residence. The electricalrequirements of the equipment and the available electrical service at each node site must beconsidered, and environmental factors such as equipment heat dissipation and the relativehumidity in which the equipment must operate must be considered. In addition, equipmentcompliances with electromagnetic interference (EMI) regulations, safety standards, andinternational input power must be known.

Physical Specifications

The following table gives equipment size, weight, and cooling information. The weightrepresents the weight of unloaded equipment; the actual weight of the equipment depends on thenumber and type of modules installed.

TABLE 2-10. Equipment Size, Weight, and Cooling_ __________________________________________________________________

Unloaded HeatHeight Width Depth Weight Dissipation

Item (inches) (inches) (inches) (pounds) (BTUs/Hour)_ ___________________________________________________________________ __________________________________________________________________Series M1 Shelf 17 30 28 150 2,550_ __________________________________________________________________Series M2 Shelf 17 30 28 175 4,000_ __________________________________________________________________Four Shelves on Base Power Unit 77.5 30 28 825 10,200–16,000_ __________________________________________________________________CO Frame with four shelves 72 35 29 850 10,200–16,000_ __________________________________________________________________Console Display Terminal 16 17 21 <50 1,360_ __________________________________________________________________

Electrical Specifications

When planning a node site, adhere to the electrical service requirements shown in the table belowand note the following:

The VAC shown under Nominal Voltage accepts 50 Hz and 60 Hz AC power (47–63 Hz).

For one to four M1/M2 Shelves on a Base Power Unit with ACD, the amperage shown underAverage Use (amps) is the average current draw for maximum configuration.

Four M1/M2 Shelves on a Base Power Unit with ACD do not provide a three-phase load, butaccept power through one leg of a 208V three-phase power cord and plug.


Node________________TABLE 2-11. Node Electrical Service Requirements

_ _____________________________________________________________________________Nominal Voltage Service Average

Item Voltage Ranges (amps) Phase Use (amps)_ ______________________________________________________________________________ _____________________________________________________________________________One to four M1/M2Shelves on Base PowerUnit with ACD

240 VAC 200 to 240 VAC 30 1 15

_ _____________________________________________________________________________Full CO FrameSeries M1 Shelves

−48 VDC −41 to −60 VDC 40 * 24*

_ _____________________________________________________________________________Full CO Frame SeriesM1/M2 Shelves (mixture)

−48 VDC −41 to −60 VDC 40 * 24*

_ _____________________________________________________________________________CRT 120 VAC – 15 1 1_ ________________________________________________________

220 VAC – 15 1 0.5_ _____________________________________________________________________________

* For CO frames containing Series M1 and/or M2, up to four power feeds are required. The first feed supplies power to the first powersupply in the Series M1 or M2 Shelf in the frame. The second power feed supplies the second power supply on each shelf. For framesthat contain only Series M1 Shelves, only three power feeds are needed to the frame. For frames with only Series M2 Shelves (whereeach shelf has four power supplies) or a mixture of Series M1 and M2 Shelves, four power feeds are required to the frame.

Each feed should draw a maximum of 40 amps; (37 amps if the frame consists of all Series M1 Shelves). A feed can be protected withcircuit breakers with a power rating as high as 60 amps. The maximum rating depends on the distance from the frame to the power

source in the CO. Consult engineering for the correct circuit breaker value for the installation.


Node________________As critical modules (such as the Switch), interface modules (which bring services such asasynchronous connections to end users), and trunks are installed in a node, their total powerconsumption cannot exceed the maximum power consumption of a node.

TABLE 2-12. Node Total Power Consumption

_ _______________________________________Overall Limits (amperes)_ __________________________

Shelf 5 VDC −12 VDC +12 VDC_ ________________________________________ _______________________________________Series M1 Shelf 80 5.2 5.8_ _______________________________________Series M2 Shelf 126 5.8 5.8_ _______________________________________

The following table provides electrical information that is important when selecting a node siteand when populating a node with critical control modules and redundant modules needed for highavailability. When planning a node site, adhere to the service requirements shown in the table andnote the following:

For BNS-2000 configurations with three Series M2 Extension Shelves, the current drawshown is for both CMA1 Switch modules and their I/O boards: two CMA1 Switch modules,Switch I/O (CNA1), Stratum 4 Clock I/O (CMC3), and backplane terminators. Both CNA1and CMC3 are required for the first Switch.

For BNS-2000 configurations with five Series M2 Extension Shelves, the current draw shownis for both CTG13 Switch modules and their I/O boards, which includes two CTG13 Switchmodules, the double board Extended Cable/Clock and RIB Status I/O Board (CNA7), and thetwo RIB boards (CUW1). The CNA7 is required for the first Switch.

The peak power requirement for the disk/tape units on an ECPU system occurs at start-up andduring tape motion. To avoid overloading +12 VDC power, do not put more than onedisk/tape drive on any one shelf. Dual disk/tape configurations require two Series M1 ControlShelves.

For ECPU configurations, Series M1 Control Shelves using the SCSI/DKI ASP4B I/O boardmust use the ASP8 tape I/O board.


Node________________TABLE 2-13. Node Module and I/O Board Electrical Service Requirements

_ ____________________________________________________________________________Module I/O Typical Current Amps_ ____________________________________________

Module Board Board +5 VDC +12 VDC -12 VDC_ _____________________________________________________________________________ ____________________________________________________________________________CCM single TN2235 CTS2 3.0 0.4 0.0_ ____________________________________________________________________________CCM dual TN2235 CTS1 3.5 0.4 0.0_ ____________________________________________________________________________CIM CMA2 CMC2 3.4 0 0_ ____________________________________________________________________________Clock TN1001B ASP1 4.0 0.0 0.0_ ____________________________________________________________________________CTRM TN2096 ASP7B 3.0 0 0_ ____________________________________________________________________________Disk TN2175B AWJ12 1.6 2.0 0.0_ ____________________________________________________________________________ECPU MC1D138A1 AWJ15 4.1 0.045 0.045_ ____________________________________________________________________________Switch TN2009 None 4.5 0.0 0.0_ ____________________________________________________________________________MRCM TN2109C AWJ16B 2.5 0.4 0.4_ ____________________________________________________________________________Repeater TN1003 ASP1 2.3 0.0 0.0_ ____________________________________________________________________________SCSI/DKI UN635B ASP4/ASP4B 4.0 0.0 0.0_ ____________________________________________________________________________M2 Switch CMA1 CNA1 12.8 0 0

Complex (Standard) CMA1 CMC3_ ____________________________________________________________________________M2 Extension Shelf CNA2 2.7 0 0_ ____________________________________________________________________________M2 Switch CTG13 12.8 0 0

Complex (Extended) CTG13 CNA7_ ____________________________________________________________________________M2 Extension Shelf CNA8 2.7 0 0_ ____________________________________________________________________________Tape Internal (CCM) TN2233 CSD9 0.7 0.37 0.0_ ____________________________________________________________________________Tape Internal (ECPU) TN2097 ASP8 2.1 2.0 0.0

AWJ12 2.1 2.0 0.0_ ____________________________________________________________________________

Environmental Specifications

The equipment room should be enclosed and have an air distribution system that providesadequately cooled, filtered, and humidity-controlled air.

CAUTION: To avoid overheating and equipment failure, adequate space for air circulationaround equipment must be maintained at all times. Consult the Site Preparationsection in this chapter for the required clearances for each piece of equipment.


Node________________TABLE 2-14. Environmental Operating Limits

_ ____________________________________________________________________________Altitude Sea level to 10,000 feet (3050 meters)_ _____________________________________________________Temperature 40°F ( 4°C) to 120°F ( 49°C)a_ _____________________________________________________

Series M1 or M2Shelves in a Node

Humidity 20% to 55% (noncondensing)b_ ____________________________________________________________________________

Notesa The tape drive (TN2097) should not be operated when the room temperature is above 100°F (38°C).b Long-term operating humidity should be 20 to 55 percent (noncondensing). Short-term operating humidity, for

periods of 72 hours or less, should be 5 to 95 percent (noncondensing), with a maximum of 15 days per yearoutside the long-term limits.

Compliances

The following tables show the electromagnetic, safety, and input power compliances met by nodeequipment. Note that the CO frame does not meet the same compliances as Series M1 or M2Shelves.

TABLE 2-15. Electromagnetic Compliances

_ ____________________________________________________________________________EMC Standard_ _____________________________________________________

FCC A DOC A VDE A CISRP22 AItem Domestic Canada International International_ _____________________________________________________________________________ ____________________________________________________________________________

Series M2 Shelf √ √ √ √_ ____________________________________________________________________________Series M1 Shelf √ √ √ √_ ____________________________________________________________________________CO Frame √ √ No No_ ____________________________________________________________________________Base Power Unit √ √ √ √_ ____________________________________________________________________________External Tape Device √ √ √ √_ ____________________________________________________________________________


Node________________TABLE 2-16. Safety Compliances

_ ____________________________________________________________________________Safety Standards_ _________________________________________________

UL CSA IECItem Domestic Canada International_ _____________________________________________________________________________ ____________________________________________________________________________

Series M2 Shelf √ √ √_ ____________________________________________________________________________Series M1 Shelf √ √ √_ ____________________________________________________________________________CO Frame √ √ No_ ____________________________________________________________________________Base Power Unit √ √ √_ ____________________________________________________________________________External Tape Device √ √ √_ ____________________________________________________________________________

TABLE 2-17. Input Power Compliance

_ __________________________________________Input Power_ ____________________

48 VDC 240 VACCO International_ ___________________________________________ __________________________________________

Series M2 Shelf √ √_ __________________________________________Series M1 Shelf √ √_ __________________________________________CO Frame √ No_ __________________________________________Base Power Unit No √_ __________________________________________External Tape Device No √_ __________________________________________


Node________________Site Preparation

This section includes the following information for both customer premises and CO sites:

basic equipment dimensions for node equipment

floor and shelf space requirements for node equipment

site preparation notes for each piece of equipment or configuration type

For more detailed information about equipment installation and/or cabling, see the DataNetworking Products Cabling Guide and the appropriate Node Reference. Observe the cablingguidelines given in these documents to provide interference-free data transmission and to meetFederal Communications Commission electromagnetic interference (EMI) regulations.

All Sites

1. All sites chosen should adhere to strict environmental requirements for altitude, temperature,and humidity. Refer to the Environmental Specifications section.

2. If a node shelf is connected to an uninterruptible power supply (UPS), the console deviceshould be connected to the UPS also. Otherwise, the console can be without power if it isneeded to maintain the node during a power failure.

3. The following figures show areas required for I/O cable egress at the top or bottom of thenode shelf. Prepare the floor or overhead cable tray access to conform to the size andlocation of the spaces allowed for cables to pass through the top or bottom of the shelf.


Node________________

Rear View

3 1/4"

I/O Cable Egress

Top View

8 1/4"

30"

17"

30"

28"

FIGURE 2-8. I/O Cable Egress from Series M1 and M2 Shelves


Node________________

Rear View

3 1/4"

I/O Cable Egress

Top View

8 1/4"

30"

9 1/2"

28"

30"

FIGURE 2-9. I/O Cable Egress from Base Power Units

4. Additional tape cartridges should be obtained for the network administrator’s use to createbackup tapes and databases. These tapes must be compatible with the 3M DC2000Gammamat Data Cartridge. They can be ordered from Lucent Technologies by specifyingCOMCODE 405177766.

5. Always keep the front doors of the node cabinets closed for better air circulation.


Node________________Customer Premises Sites

The following figures illustrate the dimensions of Series M1 Shelves in a BNS-2000 VCS site.

M1 Shelf

BasePower Unit

30"28"

9.5"

17"

FIGURE 2-10. Single BNS-2000 VCS Series M1 Control Shelf on a Power Base Unit


Node________________

30"28"

9.5"

26.5"

43.5"

60.5"

77.5"

30"

FIGURE 2-11. BNS-2000 VCS Series M1 Shelves on Base Power Units


Node________________The following figures illustrate the dimensions of Series M1 and Series M2 Shelves.

30"

M1 ControlShelf

M2 SwitchShelf

17"

17"

BasePower Unit

9.5"

28"

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

........................

........

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

........................................

................

........................

................................

........

................

................................

................

........................

........................

................

........................

................................

........

................

.. .... .... .... ..

................

........

................................

................

........................

................................

................

........

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

........................

........

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

........................................

................

........................

................................

........

................

................................

................

........................

........................

................

........................

................................

........

................

.. .... .... .... ..

................

........

................................

................

........................

................................

................

........

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................ ........................

................................

................

........................

........................

................

........................

................................

........

........

................

........

................................

................

........................

........

................................

................

.. .... .... .... ..

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................ ........................

................................

................

........................

........................

................

........................

................................

........

........

................

........

................................

................

........................

........

................................

................

.. .... .... .... ..

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

................

................

................

........

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........................

................................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

........

................

................

................

................

........

........

........

........................

................

FIGURE 2-12. Minimum BNS-2000 Node with Series M1 and M2 Shelves on BasePower Unit


Node________________

M1 PortShelf

M1 ControlShelf

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

.. .... .... .... ..

................

................................

........

........................

................

................................

........

................

........

........

................................

........................

................

........................

........................

................

................................

........................................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

........

................

................................

........................

................

................................

........

................

.. .... .... .... ..

................

........

................................

........................

................

........................

........................

................

................................

................

........

................................

........................

................

........................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

........

........ ................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

43.5"

30"

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

........................

........

........

........

................

................

................

................

........

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

.. .... .... .... ..

................

................................

........

........................

................

................................

........

................

........

........

................................

........................

................

........................

........................

................

................................

........................................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

........

................

................................

........................

................

................................

........

................

.. .... .... .... ..

................

........

................................

........................

................

........................

........................

................

................................

................

........

................................

........................

................

........................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

........

........ ................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

28"

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

.. .... .... .... ..

................

................................

........

........................

................

................................

........

................

........

........

................................

........................

................

........................

........................

................

................................

........................................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

........

................

................................

........................

................

................................

........

................

.. .... .... .... ..

................

........

................................

........................

................

........................

........................

................

................................

................

........

................................

........................

................

........................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

........

........ ................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

60.5"

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

.. .... .... .... ..

................

................................

........

........................

................

................................

........

................

........

........

................................

........................

................

........................

........................

................

................................

........................................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

........

................

................................

........................

................

................................

........

................

.. .... .... .... ..

................

........

................................

........................

................

........................

........................

................

................................

................

........

................................

........................

................

........................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

........

........ ................................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........................

................

................................

........

................

................

................

77.5"

9.5"BasePower Unit

26.5"

M2 ExtensionShelf

M2 SwitchShelf

FIGURE 2-13. Four BNS-2000 Shelves on Base Power Unit


Node________________When preparing a site for a customer premises installation, note the following:

1. For BNS-2000 and BNS-2000 VCS configurations, the shelf stack should be placed on thefloor.

For BNS-2000 and BNS-2000 VCS installations using AC power sources, the BasePower Unit is required for each stack of one to four Series M1 or Series M2 Shelves.

For installations using −48 VDC power, the CO Frame is required.

Provide mounting with suitable stability and take into account the distribution of cables fromthis unit.

The following figure shows floor plan recommendations for a large node.

2. Power distribution outlets for supplying power by line cords to node equipment andperipherals should be within 5 feet of each item.

3. Power to a stack of four Series M1 or M2 Shelves with a Base Power Unit using 208V,three-phase power should be fused at 30 amps and distributed through industrial part NEMAL21-30R. (The shelf does not impose a three-phase load, but uses one leg of a three-phasepower cord and plug.)

4. Power to a stack of four Series M1 or M2 Shelves with a Base Power Unit using 200–240V,single-phase power should be fused at 30 amps and distributed through industrial partNEMA L14-30R.


Node________________

3 Feet Minimum

Equipment Room Clearances

Rear

Node

Front

Data SetCabinet

3 Feet Minimum5 Feet Recommended

CRT CRT

TypicalComputer

Cab. 0-3 Cab. 4-7

Node

FIGURE 2-14. Customer Premises Floor Plan


Node________________CO SitesThe following figure illustrates the dimensions of four shelves mounted in a frame suitable for aBNS-2000 or BNS-2000 VCS CO installation.

84"

35"

29"

12"

72"

1/2"

FIGURE 2-15. Four BNS-2000 or BNS-2000 VCS Shelves Mounted in a CO Frame


Node________________When preparing a BNS-2000 or BNS-2000 VCS site for a CO installation, note the following:

1. When a BNS-2000 VCS node consists of two CO frames, the associated shelves must beplaced in adjacent locations. The second shelf frame must be to the right of the first one, asviewed from the work aisle at the front of the shelves.

2. When a BNS-2000 node consists of two CO frames the associated shelves may be locatedtogether, or wherever it is convenient to put them, within the distance allowed by cablelength restrictions.

The multi-coax cabling from the Switch Shelf to an Extension Shelf reaches up to 10 feet.The best arrangement is to keep all Series M2 Shelves in the same stack. Series M1 Shelvescan be located anywhere within the maximum length of the fiber optic cable between a CIMon the Switch Shelf and a CTRM in the Series M1 Shelf.

The following figures show possible CO floor plans for one- and two-frame configurations.

Maintenance Aisle3 Feet Minimum


Front

Work Aisle3 Feet Recommended

OtherEquipment

FrameCRT

Rear

CO Frame

FIGURE 2-16. CO Floor Plan—Single CO Frame

3. The console device for a single or dual CO frame configuration may be placed on a table orpedestal next to the node. It also may be placed across the aisle or in another nearbylocation.


Node________________

3 Feet Minimum


Rear

Node

Front

Data SetCabinet


CRT CRT

OtherEquipment

FrameFrame 0 Frame 1

Node

FIGURE 2-17. CO Floor Plan—Two CO Frames

4. The node and C-VDM cabinets are common system equipment. Therefore, their input powerfeeder should originate at the power distribution source serving other common systemequipment in the CO.

NOTE: Never use -48 VDC filtered battery power ("talk" battery) for these circuits.Filtered battery is used to supply power to the customer "tip" and "ring" circuits,and it is not compatible with BNS-2000 or BNS-2000 VCS equipment.

The following power distribution sources can be used to power the node and associatedequipment in the CO:

−48 VDC and return from the Battery Distribution Fuse Board (BDFB) or power boarddistribution (PBD) for BNS-2000 and BNS-2000 VCS CO sites.

220 VAC from the power distribution service cabinet (PDSC) protected by the CO dieselgenerator or the Emergency AC power plant (523A or similar) for BNS-2000 and BNS-2000 VCS CO sites.


Node________________Ground feeders must be obtained from a common ground source (CO ground). AllBNS-2000 and BNS-2000 VCS equipment requires framework ground connections. Wheninstalled properly according to instructions in the Node Reference, BNS-2000 and BNS-2000VCS frames provide a continuous signal and electrical ground with multiple paths throughall shelves.

See BCP 802-001-196 Grounding of Data Processing Equipment for detailed groundingrequirements.

5. A fuse and alarm panel is provided for the CO frame with the -48 VDC power option toconnect power to each shelf or modular cabinet.

6. Power to each BNS-2000 and BNS-2000 VCS −48 VDC frame must be provided on fourseparate circuits, each fused for a maximum of 60 amps. (Three feeds are required foroperation; one is required for redundancy.) All feeds must be provided with approvedovercurrent protection, with a rating not to exceed 60 amps. For a maximum configurationoperating on three feeds, 37 amps is required for each feed. Average use running on fourfeeds is 24 amps per feed.

7. Power to the peripherals (the console, printer, and external tape device) should be distributedthrough standard National Electrical Manufacturers Association (NEMA) 5-15R outlets(120V, 15 amps).

8. When properly installed according to the instructions in the Node Reference, the COconfiguration meets earthquake bracing specifications in the Bellcore Network Equipment-Building System (NEBS) Generic Equipment Requirements.

9. The BNS-2000 and BNS-2000 VCS CO frames are shipped with an extension hood for thetop of the frame (Figure 2-15). When installed, the extension raises the overall equipmentheight to 84 inches, for installation in a row of seven-foot equipment racks. In addition,Figure 2-15 shows the CO frame as it appears on a level surface. In some installations, theframe is positioned within a lowered area that obscures the frame base, so it does not appearexactly as shown in this figure.

Peripheral Equipment

Administering the node effectively requires the following peripheral equipment:

A Model 715 Business Communications Terminal (or the equivalent) for use as a ControlComputer console. This console is the operations input device for the node.

A serial printer with an RS-232-C interface to provide a hard copy record of operations andmaintenance activities. Any ASCII serial printer can be used.


________________Concentrators and Multiplexers

Concentrator and Multiplexer Types 3-3Architecture 3-3Limits 3-4Other Considerations 3-5

Critical Equipment Design 3-5Link Speeds and Redundancy 3-5Dual Link Option 3-6Cold Standby Link 3-6Dial-Back Recovery 3-7Power Configurations 3-7

Cabinet Design 3-8Cabinet Arrangements 3-8Module Placement Options and Restrictions 3-9

Electrical Specifications and Compliances 3-12Physical Specifications 3-13Electrical Specifications 3-13Environmental Specifications 3-16Compliances 3-16

Site Preparation 3-17BNS-2000 MPC Site 3-18SAM504 Site 3-19SAM64 Site 3-23SAM16 Site 3-24


________________Concentrators and Multiplexers

This chapter explains how to plan the overall design of a concentrator or multiplexer configuredin a Data Networking Products network. It gives specifications for concentrator and multiplexerequipment, including height and weight, electrical requirements, and capacities; and it covers siteplanning and design issues. Other aspects of concentrators and multiplexers are treatedelsewhere, as follows:

Concentrator links to nodes are explained in the Trunks chapter.

Spare parts information is provided in Appendix A.

In addition, the System Description for the node contains a complete explanation of eachsupported concentrator or multiplexer and the module reference for the particular concentrator ormultiplexer contains more details on installation, cabling, and administration guidelines.

Concentrator and Multiplexer Types

Concentrator selection is based on such factors as distance between the concentrator and node,services required at the concentrator site, and number and type of connections required. BNS-2000 and BNS-2000 VCS support two families of concentrators:

Multipurpose Concentrator (MPC) supports most services available in the node through asubset of the interface modules that can reside in the node. User connections to theconcentrator is through ports located on these interface modules. Both fiber and wire links aresupported between the BNS-2000 MPC and the home node. The BNS-2000 MPC contains 15slots.

Synchronous/Asynchronous Multiplexers (SAMs), which are available in 504, 64, and 16-portversions, support EIA RS-232-C synchronous transport and/or switched asynchronousconnections, administrable on a per port basis. The SAM504 and SAM64 can be linked to thehome node by fiber or wire facilities, and the SAM16 by a wire facility only. A dual wire linkis an option for the SAM16 and SAM64.

Architecture

Concentrators and multiplexers are remotely located shelves and cabinets that contain slots forinterface modules for user services. They operate by concentrating or multiplexing user data overthe link to the home node. They extend the distribution limit of network interfaces beyondconventional connection distances. Concentrators and multiplexers rely on the home node towhich they are connected for control functions. A concentrator or multiplexer cannot be directlyconnected to another concentrator or multiplexer because traffic must be switched through thehome node.


Concentrators and Multiplexers________________The following table summarizes the concentrator and multiplexer services and the types of linkssupported by each.

TABLE 3-1. Concentrator and Multiplexer Architecture Overview

_ _______________________________________________________Service

Device Technology Provided Links_ ________________________________________________________ _______________________________________________________BNS-2000 Concentrator and All node services fiber

MPC multiplexing data except those provided wire

by Series M2 modules

or DKAP module_ _______________________________________________________SAMs Time and channel Switched or dedicated fiber

division multiplexing; asynchronous connections wire

point-to-point or transparent synchronous

multiplexing via VDMs connections_ _______________________________________________________

Limits

Each concentrator and multiplexer supports different numbers and types of interfaces. Thefollowing table summarizes other critical differences.

TABLE 3-2. Concentrator and Multiplexer Interface Overview

_ _____________________________________________________________Concentrator or Interface Interface

Multiplexer Modules Ports Speed Throughput_ ______________________________________________________________ _____________________________________________________________BNS-2000 12 modules Depends on Depends on Depends on

MPC modules modules modules_ _____________________________________________________________SAM504 16 TERM32s 504 19.2 Kbps 95% of 9.6 Kbps

per port full duplex/port_ _____________________________________________________________SAM64 2 TERM32s 64 19.2 Kbps 95% of 9.6 Kbps

per port full duplex/port_ _____________________________________________________________SAM16 2 CPY1 16 19.2 Kbps 100 Kbps

Modules per port per CPY1_ _____________________________________________________________


Concentrators and Multiplexers________________The node configuration database limits the total number of modules residing in concentratorslinked to a node. This limit is the result of the number of remote modules. It includes allmodules, even the Switch, Clock, and trunk modules. It also includes TERM32s in SAMs andBSC control units (CUs) connected to a node or concentrator. The default limit, which is also themaximum limit, is 452 modules in concentrators.

The default values of the database also limit the number of BNS-2000 MPCs and SAMsconnected to a node, in any combination. Other modules affect this limit, too. The default limitis 253. Resizing can increase this only to 254.

Other Considerations

By adding the appropriate Control Computer hardware and software, a BNS-2000 MPC can beupgraded to a BNS-2000 VCS or BNS-2000 Series M1 Control Shelf. Because the CCM canphysically reside in a BNS-2000 MPC, it can be upgraded to BNS-2000 or BNS-2000 VCS CCMsystems.

A BNS-2000 MPC can also be upgraded to a BNS-2000 VCS Series M1 Port Shelf by adding aRepeater module or to a BNS-2000 Series M1 Port Shelf by adding a CTRM and otherappropriate critical modules.

Most user services provided by the interface modules can be provided via a BNS-2000 MPC,except those provided by the DKAP and the Series M2 interface modules. The interface moduleand I/O boards are interchangeable.

Critical Equipment Design

Power supplies and link availability are critical to concentrator functioning and to supplying end-user services. Both power supplies and link interface modules (trunk modules) reside in theconcentrator. In addition, configurations including external equipment, such as modems, alsoensure concentrator availability. The various options of equipment critical to concentratoravailability should be carefully considered and well planned.

Link Speeds and Redundancy

The concentrators and multiplexers support a variety of trunk links back to the home node as wellas link redundancy options. The following table summarizes the differences. Link redundancyoptions are summarized in the following sections; the appropriate concentrator references providemore details.


Concentrators and Multiplexers________________TABLE 3-3. Concentrator and Multiplexer Link Interfaces

_ ________________________________________________________________________Number Link Link Type of Link

Device of Links Type Speed Redundancy_ _________________________________________________________________________ ________________________________________________________________________BNS-2000 1 or 2 Fiber (SFT) or 8 Mbps Fiber; Cold Standby Link

MPC Wire (SWT) up to 2 Mbps Wire or Dial Back Recovery_ ________________________________________________________________________SAM504 1 Fiber (HS-Trunk) or 8 Mbps Fiber; Dial Back Recovery

Wire (T1-Trunk, SAMSL) up to 2 Mbps Wire_ ________________________________________________________________________SAM64 1 or 2 Fiber (HS-Trunk) or 8 Mbps Fiber; Dual Wire Link

Wire (T1-Trunk, SAMSL, up to 2 Mbps Wire Option with

or SAMDL) SAMDL_ ________________________________________________________________________SAM16 1 or 2 Wire (Integrated Up to 2 Mbps; Dual Wire Link

Trunk) Wire Option_ ________________________________________________________________________

Dual Link Option

The SAM16 and SAM64 support a dual wire link option. Two trunk links are connected from theconcentrator to the same home node. The nodes are configured in a dual operational mode.Traffic is sent over both links when they are operational. On the failure of one of the links, alltraffic is automatically diverted to the second link.

NOTE: Although two links are connected to the node, the link speed should be engineered soone link can carry all traffic between the concentrator and the node. Otherwise, flowcontrol of traffic results from a single link failure.

Cold Standby Link

The BNS-2000 MPC supports an optional redundant wire/fiber link through a cold standby linkinterface module. This cold standby link can reside in slots allocated for use by a link module. Ifthe primary link fails, the network administrator can manually restore the BNS-2000 MPC byestablishing a link with the cold standby. This manual restoration is done by changing theconcentrator address from the address of the failed link to the address of the cold standby linkwith the move module or change concentrator command and then the restore concentratorcommand. If modules are residing in the concentrator that are accessed by physical addresses, thephysical addresses must be changed as well.


Concentrators and Multiplexers________________NOTE: When a cold standby link is in use, physical addressing is not recommended because

the address of the backup link differs from the address of the failed link because thebackup link resides in a different slot. If a device on a BNS-2000 MPC is administeredas a PDD, which uses physical addressing, the call to that physical address will fail. If adevice on a BNS-2000 MPC is addressed by its service address, the call will becompleted. In addition, addressing information on billing and measurement reportschanges when the cold standby link is in use.

Dial-Back Recovery

For all concentrators and multiplexers with wire links, external dial-back modems configured onthe facility link can provide dial backup recovery for the link. They detect a link failure andattempt to reestablish a connection to the partner-modem. These dial-back modems are usedwith an administrable timer parameter. The parameter value administered equals the maximumtime (in seconds) that should elapse before a link facility failure is detected. If the modem re-establishes the link successfully before the concentrator timer parameter expires, calls over thelink are not taken down. If the modems cannot reestablish their link, the calls are taken down.

Power Configurations

Power configuration depends on concentrator type and the environment (CP or CO) in which aconcentrator is configured. The following paragraphs summarize the options; the appropriateconcentrator references provide more details.

The BNS-2000 MPC houses two required and one optional AC or DC power supplies. Thechoice depends on the input power available and whether the BNS-2000 MPC is stacked in a COframe. In any CP or CO configuration, three power supplies minimize downtime because twopower supplies can carry the current load while the third is being replaced.

With SAMs, choices of AC or DC power must be planned: the SAM16 has one AC or DCpower supply; the SAM64 has one AC or DC power supply and optional redundant AC or DCpower supply; and a fully configured SAM504, which is used primarily in CO environments, hasfour DC power supplies. A SAM504 with six or fewer TERM32s requires one less 5-volt powersupply. (See Figure 3-5.)

When a SAM504 is configured with VDM equipment, the VDM adds three DC power supplies tothe SAM504 configuration. One VDM bay is equipped with three VDM power supplies. Asecond optional VDM bay is equipped with three VDM power supplies and can optionally beequipped with three redundant power supplies. Therefore, a two-bay VDM-SAM504configuration can house a maximum of nine power supplies.


Concentrators and Multiplexers________________Cabinet Design

Cabinet configurations depend on the number of concentrators used and the environment in whichthe concentrator is to be configured. The following sections explain these distinctions in detailand the table summarizes the choices.

TABLE 3-4. Concentrator/Multiplexer Cabinet Distinctions

_ ____________________________________________________________Installation_ _________________________________

RackConcentrator Environment Floor Rack Mount_ ____________

Type CP CO Table Stackable Mount Only_ _____________________________________________________________ ____________________________________________________________BNS-2000 MPC √ √ √ √ √ √_ ____________________________________________________________

SAM16 √ √ √ No No No

SAM64 √ √ √ No √ No

SAM504 No √ No No √ √VDM-SAM504 No √ No No √ √_ ____________________________________________________________

Cabinet Arrangements

Concentrator cabinet arrangements often depend on whether the concentrator is configured in acustomer premises or CO environment and whether the concentrator can be stacked with a likeconcentrator.

BNS-2000 MPC Cabinet

In the CP environment, a single BNS-2000 MPC must be installed on the floor, two BNS-2000MPCs can be bracketed together, or up to four BNS-2000 MPCs can be stacked on top of a BasePower Unit and bracketed together. The Base Power Unit supplies power options such as ACdistribution. Base Power Units are required for one to four BNS-2000 MPCs. Refer to the NodeReference for more details on Base Power Unit options and power components.

In the CO environment, one to four BNS-2000 MPCs are installed in a 78-inch CO frame. Aframe extension is available to raise the top of the frame to seven feet for sites requiring thatheight. Additional components, such as an optional Alarm Relay Unit (ARU), are included. Theoptional ARU is mounted in the CO frame and connects to the control cabinet.

SAM Cabinets

The SAM16 is housed in a desktop cabinet that can be mounted on a table or flat surface.

The SAM64 is designed for operation in a customer premises or CO environment. In a customerpremises environment, the SAM64 can be placed on the floor, on a table, on a rack, or on otherequipment, providing forced air from that equipment is not directed at the SAM64 unit. In the


Concentrators and Multiplexers________________CO environment, the SAM64 can be rack mounted.

The SAM504 is housed in the ESS Switch single-bay frame. When a SAM504 is configured witha VDM (VDM-SAM504), one VDM bay is required; a second VDM bay is optional. Themaximum configuration consists of two VDM bays.

Module Placement Options and RestrictionsThe options and restrictions imposed upon BNS-2000 MPCs involve placing certain modules incertain slots. The options and restrictions imposed upon SAM16 and SAM64 involve the numberof user interface modules to be configured and those imposed upon the SAM504 involve themultiplexer shelf.

BNS-2000 MPC Restrictions

BNS-2000 MPC slot numbers range from 0 through 15. (Physically, the BNS-2000 MPC isequivalent to a Series M1 Shelf.) Refer to the following figure and sections for restrictions.

POWERSUPPLY

POWERSUPPLY

POWERSUPPLY

SWITCH

POWERControl POWER POWER0 1

SWITCH

2

*3___4

*5___6 7___8 9___10 11

SWT

or

SFT

CLOCK

ESD

ESD Documentation12 13 14 15

FIGURE 3-1. BNS-2000 MPC Slot Allocation

Power Supplies. Each BNS-2000 MPC cabinet houses three power supplies. The first tworequired power supplies are housed in the first two non-addressable, non-numbered slots. Thenext addressable and numbered slot, slot 0, is reserved for the third, optional power supply.

Switch. The Switch module, which does not have an I/O board, must always occupy slot 1.A redundant Switch module is not supported.


Concentrators and Multiplexers________________Clock. The Clock module, along with its I/O board, must occupy slot 15.

Links. A minimum of one link (trunk module) must connect the BNS-2000 MPC to its homenode. The link module can be installed in slots 2, 3, 13, or 14. The primary link interfacemodule usually resides in slot 14; one of the remaining slots can house an optional cold standby.

Remaining Modules. The slots not occupied by the power supplies, the Switch, the Clock,and the link and its spare are available for supported interface modules.

SAM Restrictions

SAMs have individually addressable port connections that are made available through theirresident interface modules; they do not have addressable slots. Restrictions involving SAMcabinet and circuit board configurations follow.

SAM16 and the CPY1. The CPY1 is the SAM16 interface module. Each CPY1 containseight ports; so two CPY1s must be used in one SAM16 configuration.

POWERINPUT

100-120V200-240

50/60 HZ

2A/1A

RS232 TRUNK

A B

16 14 12 1015 13 11 9

8 6 4 27 5 3 1

FIGURE 3-2. SAM16 Rear View (Dual RS-232-C Link Option)

SAM64 and the TERM32. The TERM32 is the SAM64 interface module. It provides 32asynchronous/synchronous port connections. For 64 port connections, two TERM32s arerequired.


Concentrators and Multiplexers________________TRUNK TERM32 POWER

SUPPLYTERM32TCONB

FAN UNIT

Front View(Cover Removed)

MODEL NO.J1P186J-1SD2P100-02 J7 J8 J2 J1

100-200200-24050/60 HZ3 AMPS

J10 J9 J3J4

FIBERTRUNK

J11 J6 J5

LOOPLOOP

NORMALMUTE

RCVR

XMTR

Rear View

FIGURE 3-3. SAM64 Front and Rear Views

SAM504 Multiplexer Shelf. The SAM504 Multiplexer Shelf has front and rear slots thatsupport a maximum of 22 circuit packs. The slots are numbered beginning with slot 010 andcontinue in multiples of eight to slot 034. After slot 034, the device interface slots begin at slot040 and continue in multiples of eight to slot 178.

The front slots house the Time Division Multiplexed (TDM) Bus Controller (TCONC), atrunk/link module, up to 16 TERM32 interface modules (UN315s), and power supplies.

The rear slots house I/O distribution boards for connections to endpoint devices and linkfacilities. A printed circuit backplane separates the front and rear of the shelf.

Slots 1 and 22 house the +5.0A and +5.0B power supplies. Slots 2 and 21 house the +12 VDCand −12 VDC power supplies. The +5.0A VDC, +12 VDC, and −12 VDC power supplies areinterlocked; the fourth power supply, +5.0B, is separate. (Note: The rightmost 5-volt powersupply is not required for a SAM504 equipped with six or fewer TERM32s.)

The +5 volt power supply in slot 010 powers multiplexer shelf slots 026 through 080. IfTERM32s are installed in slot 088 or higher, an additional +5 volt power supply must be installedin slot 178 when the seventh TERM32 is installed.

A maximum SAM504 configuration consists of 15 TERM32s with 32 ports each and oneTERM32 with 24 ports. (If the SAM504 is configured with a SAMML, only 19 ports on thesixteenth TERM32 can be administered.)


Concentrators and Multiplexers________________

PowerSupplies

+5.0A +12.0 TRUNK TCONC TERM 32 –12.0 +5.0B

PowerSupplies

TERM32s

*TN

1392

TN

1394

C

* or TN1391 or MC1D090A1

FIGURE 3-4. SAM504 Multiplexer Shelf

Electrical Specifications and Compliances

When planning a network and each node site, the size and weight of each piece of equipmentmust be considered before the initial installation and for long-term residence. The electricalrequirements of the equipment and the available electric at each node site must be considered, andenvironmental factors such as equipment heat dissipation and the relative humidity in which theequipment must operate must be planned. In addition, equipment compliances withelectromagnetic interference (EMI) regulations, safety standards, and international input powermust be known.


Concentrators and Multiplexers________________Physical Specifications

The following table provides equipment size, weight, and cooling information. The weightrepresents the weight of unloaded equipment; the actual weight of the equipment depends on thenumber or type of modules installed.

TABLE 3-5. Concentrator Size, Weight, and Cooling

_ _____________________________________________________________Unloaded Heat

Height Width Depth Weight DissipationItem (inches) (inches) (inches) (pounds) (BTUs/Hour)_ ______________________________________________________________ _____________________________________________________________

BNS-2000 MPC 17 30 28 150 2,550_ _____________________________________________________________SAM16 4.4 17 13 7 100_ _____________________________________________________________SAM64 13.1 11.5 19.5 60 475_ _____________________________________________________________SAM504 (in CO frame) 84 26 24 500 3,570_ _____________________________________________________________VDM Cabinet 84 22 24 300 4,420_ _____________________________________________________________VDM-SAM504 84 26 24 800 7,990_ _____________________________________________________________

Electrical Specifications

The following tables provide electrical information that is important when selecting aconcentrator or multiplexer site and when populating the equipment with modules.

TABLE 3-6. International Input Power Compliance

_ ____________________________________________________________________________Input Power_ _______________________________________________________

48 VDC 100 VAC 120 VAC 240 VACCO Japan Domestic International_ _____________________________________________________________________________ ____________________________________________________________________________

BNS-2000 MPC √ — — √_ ____________________________________________________________________________Base Power Unit No — — √_ ____________________________________________________________________________SAM16 √ √ √ √_ ____________________________________________________________________________SAM64 √ √ √ √_ ____________________________________________________________________________SAM504 √ No No No_ ____________________________________________________________________________VDM-SAM504 √ No No No_ ____________________________________________________________________________


Concentrators and Multiplexers________________When planning a node site, adhere to the service requirements shown and note the following:

The VAC shown under Nominal Voltage accepts 50 Hz and 60 Hz AC power (47–63 Hz).

Power for the -48 VDC option requires separate power to each cabinet, 30 amps per cabinetfeed. Average use is 15 amps per cabinet.

The VDM-SAM504 contains a C-VDM and SAM504 in one frame. Each device requires aseparate power source. Use both SAM504 and VDM Cabinet entries for details.

TABLE 3-7. Concentrator and Multiplexer Electrical Service Requirements

_ _____________________________________________________________________________Nominal Voltage Service Average

Item Voltage Ranges (amps) Phase Use (amps)_ ______________________________________________________________________________ _____________________________________________________________________________BNS-2000 MPC 220 VAC 184 to 250 VAC 15 1 3_ ________________________________________________________

−48 VDC −41 to −60 VDC 18.8 – 11.3_ _____________________________________________________________________________SAM16 110 VAC 90 to 250 VAC 2 1 1_ ________________________________________________________

220 VAC 1_ ________________________________________________________−48 VDC −42 to −60 VDC 5_ _____________________________________________________________________________

SAM64 120 VAC 90 to 132 VAC 10 1 2_ ________________________________________________________240 VAC 180 to 264 VAC 10 1 1_ ________________________________________________________−48 VDC −42 to −60 VDC 10 – 3.5_ _____________________________________________________________________________

SAM504 −48 VDC −42 to −56 VDC 30 – 22_ _____________________________________________________________________________VDM Cabinet −48 VDC −44 to −58 VDC 30 – 25_ ________________________________________________________

120 VAC 90 to 132 VAC 30 1 12_ ________________________________________________________220 VAC 207 to 253 VAC 20 1 2.5_ _____________________________________________________________________________


Concentrators and Multiplexers________________As critical modules (such as the Switch), interface modules (which bring services such asasynchronous connections to end users) and concentrator links are installed in a BNS-2000 MPC,their total power consumption cannot exceed the maximum power consumption of a BNS-2000MPC.

TABLE 3-8. BNS-2000 MPC Total Power Consumption

_ _________________________________BNS-2000 MPC Overall Limits (amperes)_ _________________________________

5 VDC −12 VDC +12 VDC_ __________________________________ _________________________________80 5.2 5.8_ _________________________________

When planning a node site, adhere to the service requirements for the BNS-2000 MPC shown inthe following table.

TABLE 3-9. BNS-2000 MPC Module and I/O Board Electrical Service Requirements

_ ____________________________________________________________________________Module I/O Typical Current Amps_ ___________________________________________________

Module Board Board +5 VDC +12 VDC -12 VDC_ _____________________________________________________________________________ ____________________________________________________________________________Clock TN1001B ASP1 4.0 0.0 0.0_ ____________________________________________________________________________Switch TN1002B None 5.1 0.0 0.0_ ____________________________________________________________________________


Concentrators and Multiplexers________________Environmental Specifications

The equipment room should be enclosed and have an air distribution system that providesadequately cooled, filtered, and humidity-controlled air.

CAUTION: To avoid overheating and equipment failure, adequate space for air circulationaround equipment must be maintained at all times. Consult the Site Preparationsection in this chapter for the required clearances for each piece of equipment.

TABLE 3-10. Environmental Operating Limits

_ ____________________________________________________________________________Altitude Sea level to 10,000 feet (3050 meters)_ ________________________________________________

BNS-2000 MPCs and SAMs Temperature 40°F ( 4°C) to 120°F ( 49°C)_ ________________________________________________Humidity 20% to 55% (noncondensing)a_ ____________________________________________________________________________

Notea Long-term operating humidity should be 20 to 55 percent (noncondensing). Short-term operating humidity, for

periods of 72 hours or less, should be 5 to 95 percent (noncondensing), with a maximum of 15 days per yearoutside the long-term limits.

Compliances

The following tables show electromagnetic, safety, and input power compliances met byconcentrator and multiplexer equipment. Note that the SAM504 and VDM-SAM504 do not meetthe same compliances as the BNS-2000 MPC, SAM16, and SAM64.

TABLE 3-11. Electromagnetic Compliances

_ ____________________________________________________________________________EMC Standard_ ________________________________________________________

FCC A DOC A VDE A CISRP22 AItem Domestic Canada International International_ _____________________________________________________________________________ ____________________________________________________________________________

BNS-2000 MPC √ √ √ √_ ____________________________________________________________________________Base Power Unit √ √ √ √_ ____________________________________________________________________________SAM16 √ √ √ √_ ____________________________________________________________________________SAM64 √ √ √ √_ ____________________________________________________________________________SAM504 No No No No_ ____________________________________________________________________________VDM-SAM504 No No No No_ ____________________________________________________________________________


Concentrators and Multiplexers________________TABLE 3-12. Safety Compliances

_ ____________________________________________________________________________Safety Standards_ ____________________________________________________

UL CSA IECItem Domestic Canada International_ _____________________________________________________________________________ ____________________________________________________________________________

BNS-2000 MPC √ √ √_ ____________________________________________________________________________Base Power Unit √ √ √_ ____________________________________________________________________________SAM16 √ √ √_ ____________________________________________________________________________SAM64 √ √ √_ ____________________________________________________________________________SAM504 No No No_ ____________________________________________________________________________VDM-SAM504 No No No_ ____________________________________________________________________________

Site Preparation

This section presents the equipment dimensions, site preparation, and floor plan requirements forCP and CO sites. It includes the following information:

basic equipment dimensions

floor and shelf space requirements

site preparation notes

For detailed information about equipment installation and/or cabling, see the Data NetworkingProducts Cabling Guide, the Data Networking Products Multipurpose Concentrator Reference,and the Data Networking Products Synchronous/Asynchronous Multiplexer Reference. Observethe cabling guidelines given in these documents to provide interference-free data transmission andto meet Federal Communications Commission electromagnetic interference (EMI) regulations.

All sites chosen should adhere to strict environmental requirements for altitude, temperature, andhumidity. (See Environmental Specifications.) The front doors on all equipment cabinets shouldalways be kept closed for better air circulation.


Concentrators and Multiplexers________________BNS-2000 MPC Site

The following figure illustrates the dimensions of a BNS-2000 MPC.

M1 Shelf

BasePower Unit

30"28"

9.5"

17"

FIGURE 3-5. BNS-2000 MPC Front View

When preparing a site for a BNS-2000 MPC installation, note the following:

1. The BNS-2000 MPC must be placed on the floor; or two BNS-2000 MPCs can be bracketedtogether.

For installations using AC power sources, the Base Power Unit is required for each stackof one to four BNS-2000 MPCs.

Power to a stack of four BNS-2000 MPCs with a Base Power Unit using 208V, three-phase power should be fused at 30 amps and distributed through industrial part NEMAL21-30R. The BNS-2000 MPC cabinet does not impose a three-phase load, but uses oneleg of a three-phase power cord and plug.

Power to a stack of four BNS-2000 MPCs with a Base Power Unit using 200–240V,single-phase power should be fused at 30 amps and distributed through industrial partNEMA L14-30R.

For installations using −48 VDC power, the CO Frame is required.

2. Provide mounting with suitable stability and take into account the distribution of cables fromthis unit.


Concentrators and Multiplexers________________SAM504 Site

The following figures illustrate the dimensions of a SAM504 and a possible floor plan.

12 1/2”5”

BackFront

4 1/2”

2 3/4”3 1/4”

84” High

SIDE VIEWTOP VIEW

8 3/8”

8 3/8”

23 1/2”

17 1/2”

24”

23 1/2”

Frame extenderbrings overalldepth to 24”

26”WidthFront

6”

FIGURE 3-6. SAM504


Concentrators and Multiplexers________________

3 Feet Minimum


Front


OtherEquipment

Frame

Rear

SAM504

C-VDMCabinet

Data SetCabinet

FIGURE 3-7. SAM504 Floor Plan

The SAM504 meets NEBS earthquake specifications when mounted in a CO environment per theLucent Technologies installation instructions. When preparing a site for a SAM504 installation,note the following:

1. The SAM504 is installed in an ESSTM Switching Equipment Single Bay Frame (ED5A001-70,G4). The frame is equipped with appliance outlet base covers that extend frame depth to24 inches to protect the 21-inch deep SAM504.

2. The rightmost 5-volt power supply (in the multiplexer shelf) is not required for a SAM504equipped with six or fewer TERM32s. This power supply serves TERM32 slots 7through 16.

3. Input wiring from the fuse box to the SAM is not provided.

4. Power to the SAM504 with -48 volt DC power should be fused at 30 amps.


Concentrators and Multiplexers________________Adding Voice Data Multiplexers (C-VDM or VDM-SAM504)

The following figure illustrates the dimensions of a VDM-SAM504.

84" High

26" Wide

24" Deep

FIGURE 3-8. VDM-SAM504

When preparing a CO site for VDM installation, modular cabinets, SAM504 cabinets, VDM-SAM504 cabinets, CO VDMs, and the data set cabinet or rack (dial-in and dial-out modems andT1 or 56kbps DSUs) should be located in the same lineup for maintenance ease and to share thesame cable rack.


Concentrators and Multiplexers________________1. When configuring a system with a single cabinet frame, the adjacent space to the right of that

frame should be reserved for the possible addition of a second cabinet frame.

2. C-VDM or VDM-SAM504 frames can be added on either side of the node cabinets, or on aseparate aisle. However, the following recommendations are made:

C-VDM cabinets should be kept adjacent to the node cabinets and to other VDM cabinetsto minimize cabling and make servicing easier.

C-VDM cabinet growth can occur in one direction if only a few cabinets are used. Asmore cabinets are added, an equal distribution of cabinets on either side of the nodecabinets is recommended to reduce cabling.

The addition of CO VDMs (C-VDMs) to either model SAM should follow guidelines setfor the node.

If both a C-VDM and SAM504 are to be ordered, consider ordering a VDM-SAM504 toreduce equipment cost and floor space consumption, and to simplify cablingrequirements.

The following figure shows a possible multiple cabinet CO frame configuration incorporatingthree bays of VDMs. While configurations vary depending on available floor space and potentialsystem growth, this example demonstrates a balanced plan.

_ ____________________________________________________________________________

Future Initial Data Modular Cabinet Modular Cabient FutureVDM VDM Set or or VDM

Expansion or Rack Series M1 Shelf Series M1 Shelf ExpansionVDM-SAM504 0 to 3 4 to 7

_ ____________________________________________________________________________

FIGURE 3-9. Configuration with VDM Cabinets



The following figure illustrates the dimensions of a SAM64.

19.5”

13.1” TR

UN

K

TC

ON

TE

RM

32

OP

TIO

NA

L T

ER

M32

PO

WE

RS

UP

PLY

11.5”

Allow three to six inches space for cables at the rear of each unit.

FIGURE 3-10. SAM64

When preparing a site for a SAM64 installation, note the following:

1. The SAM64 cabinet can be placed on a table or other level surface that can support itsweight and allow access, such as a shelf. (To avoid confusion, "shelf" does not mean arack-mount equipment shelf, but an ordinary shelf.) Never stack one SAM64 on top ofanother. Provide a location with suitable stability and account for cable distribution.

2. Allow three inches above the unit and on both sides for ventilation. Make sure the bottomvents are not blocked by nearby objects.

3. Cabling connections are at the rear of the SAM64 cabinet. Allow three to six inches at therear of each unit for cables.



The following figure illustrates the dimensions of a SAM16.

POWERINPUT

100-120V200-24050/60 HZ

2A/1A

RS232 TRUNK

AB

16

14

12

10

15

13

11

9

8

6

4

2

7

5

3

1

4.5 "High

10"Deep

17" Wide

Allow three to six inches for cables at the rear of each unit.

FIGURE 3-11. SAM16

When preparing a site for a SAM16 installation, note the following:

1. The SAM16 cabinet can be placed on a table or other level surface that can support itsweight and allow access, such as a shelf. (To avoid confusion, "shelf" does not mean arack-mount equipment shelf, but an ordinary shelf.) Provide a location with suitable stabilityand account for cable distribution.

2. Allow three inches above the unit and on both sides for ventilation. Make sure the bottomvents are not blocked by nearby objects.

3. Cabling connections are at the rear of the SAM16 cabinet. Allow three to six inches at therear of each unit for cables.


________________Trunks

Trunk Types 4-3Trunk Limits 4-4Trunk Selection 4-7

Trunk Design Issues 4-10Specific Trunk Design Issues 4-10

Interworking 4-15Trunk Channels 4-16Trunk Active Tests 4-16

Electrical Specifications and Compliances 4-17Distance Limits and Interface Standards 4-17Electrical Specifications 4-19Electrical/Mechanical Connection Standard Compliances 4-20


________________Trunks

This chapter provides all physical and hardware-related details for trunk modules. It includesdistance limits, interface standards, electrical requirements, design issues, and interworkinginformation. Other aspects of trunks are treated elsewhere, as follows:

Trunk connections and call set-up routing are explained in the Routing chapter.

Trunk groups are explained in the Addresses and Groups chapter.

Trunk call screening security is explained in the Security chapter.

Spare parts information is supplied in Appendix A.

In addition, the System Description contains a complete list of supported trunk modules. TheData Networking Trunk Module Reference for the Series M1 trunks and for the Series M2 trunkscontains more details on installation, cabling, and administration guidelines.

Trunk Types

When selecting the trunk type, the possible trunk connections that can be made between nodesand concentrators is a primary consideration. Trunk modules are often known by the types ofconnections they make. The two standard trunk connections are the following:

Internodal trunks are trunk modules that can be used to connect two nodes. If a particulartrunk module is supported by different networks, two different network nodes can beconnected. For example: An SWT is supported in BNS-2000 and BNS-2000 VCS nodes;therefore an SWT can be used to connect a BNS-2000 node to a BNS-2000 VCS node.

Link interface modules, or LIMs, are trunk modules that are used to link a concentration device,such as a BNS-2000 MPC, to its home node. These trunk modules are called links only todistinguish them from internodal trunks.

Some devices, such as the SAM16, have an integrated LIM. Devices such as the SAM64 andSAM504 use complementary LIMs at both ends of the node-concentrator link. For example,a Trunk-T1 module is used at the node end of the link and a T1-Trunk module is used at theSAM end of the link.

Internodal trunks support CONS and/or CLNS. LIMs can only support CONS traffic. PrimaryCONS connections include asynchronous and synchronous connections, LAN interconnections,and X.25/X.25P/X.75 connections to PDNs and PSPDNs. The primary CLNS connectionincludes support of SMDS. Internodal trunks can support wire, fiber, or coaxial connections.LIMs can support wire or fiber connections. These connections are explained later in this chapter.


Trunks________________Trunk Limits

Trunk limits are determined by the nodes and/or concentrators to which the trunk or LIM caninterface, the line speed of the trunk, and the user channels that the trunk can accommodate. Thefollowing table provides speeds for trunks carrying internodal and LIM traffic. Note that CLNStraffic can only be carried to/from BNS-2000 Series M2 Shelves.

TABLE 4-1. Trunk Connectivity and Speeds

_ ___________________________________________________________________________Trunk/Link Speed Requirements (in bps)_ __________________________________________________

Series M2 Series M1/Concentrator_ __________________________________________________Network Node/ 2.048 M to 56 K andConcentrator 44.736 M 34.368 M 8 M 56 K Lower_ ____________________________________________________________________________ ___________________________________________________________________________

BNS-2000 Trunk-T3A Trunk-E3A

CONS/CLNS Trunk-T3S Trunk-E3S_ ___________________________________________________________________________BNS-2000 SFT SWT SWT

CONS Trunk-HS Trunk-T1 Trunk-64

Trunk-64

Trunk-PQ_ ___________________________________________________________________________BNS-2000

CLNS Trunk-T3I_ ___________________________________________________________________________BNS-2000 VCS SFT SWT SWT

Trunk-HS Trunk-T1 Trunk-64

Trunk-64

Trunk-PQ_ ___________________________________________________________________________BNS-2000 MPCs SFT SWT SWT_ ___________________________________________________________________________

SAMs Trunk-HS Trunk-T1 SAMSL

SAMML_ ___________________________________________________________________________


Trunks________________The physical interface to each type of trunk module is dependent on the standard interfaces foreach trunk speed.

Each CONS trunk type provides virtual channels for CONS traffic. Each channel is a two-wayvirtual path for an end-to-end connection. The following table shows the total number of channelsand the total usable channels that each trunk type can accommodate. The total channels and userchannels differ because some channels are reserved.

TABLE 4-2. Trunk Module Channels

_ ______________________________________________Total Number of

Number of UserModule Channels Channels_ _______________________________________________ ______________________________________________

SAMML 512 507_ ______________________________________________SAMSL 512 504_ ______________________________________________SFT 2048 2042_ ______________________________________________SWT 512 506_ ______________________________________________Trunk-64 512 504_ ______________________________________________Trunk-E3A 8192 8172_ ______________________________________________Trunk-E3S 8192 8172_ ______________________________________________Trunk-HS 2048 2042_ ______________________________________________Trunk-PQ 2048 2038_ ______________________________________________Trunk-T1 2048 2042_ ______________________________________________Trunk-T3A 8192 8172_ ______________________________________________Trunk-T3I 8192 8172_ ______________________________________________Trunk-T3S 8192 8172_ ______________________________________________

The following table shows the number of slots that each module and I/O board combinationrequires and the port connections that each type of trunk I/O board can accommodate.


Trunks________________TABLE 4-3. Trunk Module and I/O Board Port Connections

_ ____________________________________________________________________________Module I/O Port Connections/

Module Board Board Slots Remarks_ _____________________________________________________________________________ ____________________________________________________________________________SAMDL MC1D106A1 CEY4 1 2 RS-232-C DTE (SAM64)_ ____________________________________________________________________________SAMSL MC1D090A1B AWJ9 1 1 V.35 DTE; (integrated in SAM8)

AWJ11 1 1 RS-232-C DTE (integrated in SAM8)_ __________________________________________

CEY2 1 1 V.35 DTE (SAM64)

CEY3 1 1 RS-232-C DTE (SAM64)_ __________________________________________

EAA2 1 1 V.35 DTE (SAM504)_ ____________________________________________________________________________SAMSL-N MC1D142A1 AWJ9 1 1 V.35 DTE; node end

AWJ11 1 1 RS-232-C DTE_ ____________________________________________________________________________SAMML MC1D091A1 AWJ9 1 1 V.35 DTE

AWJ17 1 8 RS-232-C DTE_ ____________________________________________________________________________SFT MC1D085A1 AWJ3 1 Fiber Optic_ ____________________________________________________________________________SWT TN2092/ AWJ9 1 1 V.35 DTE w/wo NRZI

TN2092B AWJ10 1 1 RS-422/449 DTE w/wo NRZI

AWJ11 1 1 RS-232-C DTE w/wo NRZI

AWJ33 1 G.703/G.704/G.706 DTE_ ____________________________________________________________________________Trunk-64 MC1D105A1 AWJ9 1 1 V.35 DTE

AWJ11 1 1 RS-232-C DTE_ ____________________________________________________________________________Trunk-E3A CMA18 CMC15 1 1 E3_ ____________________________________________________________________________Trunk-E3S CMA13 CMC13B 1 1 E3_ ____________________________________________________________________________Trunk-HS TN1010 AWJ2 1 Fiber Optic; node end_ ____________________________________________________________________________HS-Trunk TN1391 ED2P47130G1 1 Fiber Optic; SAM504 end; 1km

ED2P47230G1 1 Fiber Optic; SAM504 end; 1-3km

CEY1 1 Fiber Optic; SAM64 end; 3km_ ____________________________________________________________________________Trunk-PQ MC1D152A1 AWJ24 1 1 V.35 DTE_ ____________________________________________________________________________Trunk-T1 TN1015 AWJ4 1 V.35/RS-449; node end_ ____________________________________________________________________________T1-Trunk TN1392 ED2P46530G1 1 Used with Trunk-T1, SAM504 end

ED2P49130G1 1 Used with Trunk-T1, SAM64 end_ ____________________________________________________________________________Trunk-T3A CMA18 CMC15 1 1 T3 (DS3)_ ____________________________________________________________________________Trunk-T3I CMA14 (egress) CMC6B (egress) 2 1 T3 (DS3)

CMA16 (ingress) CMC14 (ingress)_ ____________________________________________________________________________Trunk-T3S CMA13 CMC6B 1 1 T3 (DS3)_ ____________________________________________________________________________


Trunks________________Trunk Selection

The following figures help to determine which trunk should be selected and the load capacity ofthe trunk. Figure 4-1 is to be used to select a trunk to a BNS-2000 or BNS-2000 VCS node or toa SAM or a BNS-2000 MPC or an ISN concentrator. Figure 4-2 further refines selection criteriafor trunks connecting nodes. Figure 4-3 refines selection criteria for a trunk between a node and aSAM. Figure 4-4 is used to select a trunk for traffic going through a BNS-2000 Series M2 Shelf.

Trunk-HS(Fiber trunk; can only

be used when thedistance between

nodes is lessthan 3 km.)

What will trunk connect to?

Datakit VCS Node

Speed requirement?

8 Mbps

Trunk-T1

128 Kbps to2.048 Mbps

Trunk-64

64 Kbpsand less

BNS-2000 VCSor BNS-2000 Node

Series M1 Shelf

See Figure 4-2

Speed requirement?

SFT(Fiber trunk; can only



8 Mbps

SWT

2.048 Mbpsand less

ISNNode

Speed requirement?

SFT(Fiber trunk; can only


node and the concentrator

is less than 3 km.)

8 Mbps

SWT

2.048 Mbpsand less

BNS-2000MPC

SAM

See Figure 4-3

BNS-2000 NodeSeries M2 Shelf

Both nodesare BNS-2000

nodes

See Figure 4-4 See Figure 4-2

Both nodesare not

BNS-2000nodes

FIGURE 4-1. Trunk Selection Guidelines by Node Type


Trunks________________

Trunk-PQSWT

(See "Differencesbetween the SWTand Trunk-PQ")

Traffic type going over trunk?

Frame Relayor LAN Bridge

Traffic

Other Traffic

Speed requirement? Speed requirement?

Trunk-HSSFT

(Fiber trunk; can onlybe used when thedistance between


8 Mbps

Will CIR beconfiguredfor Frame

Relayendpoints?


Yes

Trunk-PQ

No

More than 506channels required?

Yes

Trunk-PQ

No

Trunk-PQSWT

(See "Differencesbetween the SWTand Trunk-PQ")

Trunk-HSSFT

(Fiber trunk; can onlybe used when thedistance between


8 Mbps



Yes

Trunk-PQTrunk-T1

(The Trunk-PQ ispreferred becausea fairer algorithm

and largerbuffering)

No


64 Kbpsand below

Yes

Trunk-T1

No

Trunk-64

FIGURE 4-2. Trunk Selection Guidelines for a Specific Traffic Type


Trunks________________Speed requirement?

Trunk-HS(Fiber trunk; can only

be used when thedistance betweenthe node and SAMis less than 3 km;only supported for

SAM504 and SAM64.)

8 Mbps 128 Kbps to2.048 Mbps

SAM type?

64 Kbpsand less

Trunk-T1(Only supported

for SAM504and SAM64)

SAM16

Is SAM16configured fora dual link?

Yes No

SAMML SAMMLSAMSL

SAM8

SAMMLSAMSL

SAM64

Is a SAMDLconfigured?

Yes No

SAMML SAMMLSAMSL

SAM504

SAMMLSAMSL

FIGURE 4-3. Link Selection Guidelines for a SAM


Trunks________________Traffic type going over trunk?

CONS only or mixedCONS and CLNS.

CLNS only

Speed requirement?

Trunk-T3I34.368 Mbps

Trunk-E3ATrunk-E3S

44.736 Mbps

Trunk-T3ATrunk-T3S

FIGURE 4-4. Trunk Selection Guidelines for a BNS-2000 Series M2 Shelf

Trunk Design Issues

Trunk design issues involve specific choices that must be made when selecting a particular kindof trunk or application. Other design issues involve choices that must be made whenadministering node and trunk parameters.

Specific Trunk Design Issues

To determine which trunk to use in a particular network/node configuration, refer to the precedingfigures and tables. When configurations offer multiple trunk choices, refer to therecommendations in the sections that follow.

The recommendations are based on assumptions about traffic patterns and acceptable delays thatmay not apply to an individual network or part of a network. They are conservative estimates,intended to provide acceptable service in the absence of detailed knowledge about thecharacteristics of traffic in a network. It is possible to exceed these recommendations in somecases without degrading performance. However, Lucent Technologies cannot recommend thatthese recommendations be exceeded unless a detailed study of the proposed networkconfiguration and traffic is performed; a Lucent Technologies Account Representative can arrangeto perform such a study.


Trunks________________Trunk-E3A/Trunk-T3A

Both the Trunk-E3A and the Trunk-T3A convert the segments received from the node backplaneinto ATM cells to be transmitted on a facility. A single virtual path (VP) is used to carry thistraffic between a pair of BNS-2000 nodes or from a BNS-2000 node to an asynchronous transfermode (ATM) switch. The VIRTUAL PATH NUMBER parameter is used to specify a number(from 1 to 31) to identify the VP over which this traffic is to travel. Only a single virtual pathidentifier (VPI) is allowed. The setting on both ends of the trunk should match.

The Trunk-E3A/Trunk-T3A resides in a Series M2 Shelf. With configurations of up to threeSeries M2 Extension Shelves, the Trunk-E3A/Trunk-T3A can reside in any numbered Series M2Shelf. With extended switch configurations of up to five Series M2 Extenstion Shelves, theTrunk-E3A/Trunk-T3A can only reside in Series M2 Shelves numbered 0, 1, 2, or 3—not shelves6 or 7.

Trunk-E3S/Trunk-T3S

The Trunk-E3S has replaced the Trunk-E3 and the Trunk-T3S has replaced the Trunk-T3.

For configurations still using the Trunk-E3 or Trunk-T3, keep the hourly average of the peakutilization below 70%. During congestion, these trunks can discard "delete eligible" frames fromFRMs before affecting other traffic. For more information, see the appropriate trunk reference.

When upgrading exchange SMDS network service to exchange access SMDS, interexchange, andintercompany SMDS, a Trunk-T3 must be upgraded to a Trunk-T3S. During this upgrade,several routing capabilities do not take effect until all Trunk-T3s are upgraded to Trunk-T3Ss.

Also, private interLATA routing capabilities do not take effect until all trunks crossing LATAboundaries in the network are upgraded from Trunk-T3s to Trunk-T3Ss and are configured for theprivate interLATA trunk application.

The Trunk-E3S/Trunk-T3S resides in a Series M2 Shelf. With configurations of up to three SeriesM2 Extension Shelves, the Trunk-E3S/Trunk-T3S can reside in any numbered Series M2 Shelf.With extended switch configurations of up to five Series M2 Extension Shelves, the Trunk-E3S/Trunk-T3S can only reside in Series M2 Shelves numbered 0, 1, 2, or 3—not shelves 6 or 7.

Trunk-T3I

The Trunk-T3I supports the North American ANSI DS3 standard interface. The Trunk-T3I carriesonly connectionless traffic at speeds up to 44.736 Mbps consistent with the Bellcore ICIspecification TR-TSV-001060. Using a BNC coaxial cable, the Trunk-T3I connection limit is900 feet.

The Trunk-T3I is a two-board downloadable module that resides in a Series M2 Shelf. It canonly be installed in Series M2 Shelf numbers 0, 1, 2, or 3; it cannot be installed in shelves 6 or 7.

Trunk-T1

For a Trunk-T1, limit the traffic to 1000 asynchronous virtual circuits. This very conservativerecommendation is for initial installations. The number of virtual circuits can be raised if actualtraffic measurements on the trunk show spare capacity.


Trunks________________SWT

For an SWT clocked at T1 rates, keep the hourly average peak utilization below 85%.

For an SWT running at 56 Kbps, use an initial load of 100 asynchronous virtual circuits. Thisvery conservative recommendation is for initial installations. The number of virtual circuits canbe increased when actual traffic measurements on the trunk show spare capacity.

For an SWT clocked at 56 Kbps, keep the hourly average peak utilization below 80%.

For an SWT clocked at 9.6 Kbps, keep the hourly average peak utilization below 55%. During acold reboot of a node, the Trunk-PQ takes longer to come up than other CONS trunk modulesbecause it is a downloadable module. If calls to PVCs or PDDs cannot be routed to a differenttrunk after a node reboot, administer addresses so the same address does not cause calls to berouted to both a Trunk-PQ and another trunk. This addressing and call routing concept is mostimportant for Frame Relay committed information rate (CIR) calls because CIR is not supportedon other trunks.

A Trunk-PQ can be overengineered when the maximum aggregate CIR is administered as anabsolute value or as a percentage to a value greater than the line speed. Once calls are set up overa trunk with a combined CIR equal to this value, subsequent calls are rejected until a CIR callcomes down and the total is reduced. The maximum aggregate CIR does not have to beadministered with the same value for both ends of the Trunk-PQ.

The combined maximum aggregate CIR and the aggregate information rate for non-CIR channelscan be no more than 1000% of the line speed. Although the maximum aggregate CIR can begreater than 100%, the instantaneous traffic from CIR calls should not exceed 100%—(aggregateinformation rate [%]) of the line speed. Traffic from CIR and non-CIR calls greater than the linespeed for a significant period of time can result in congestion and data loss.

Trunk-PQ and SWT Differences. The selection of an SWT or a Trunk-PQ requiresconsideration of operations and maintenance, throughput, channels support, and interworkingdifferences:

The improved measurements of the Trunk-PQ give utilization, byte counts, and dropped bytecounts for traffic in both directions. The dropped byte counts for Committed InformationRate (CIR) data in the transmit direction are broken down to assist in isolating CIR-relatedproblems.

To detect if T1 facility equipment has B8ZS configured properly, the network administratorcan select the all zeros pattern when running Trunk-PQ diagnostics.


Trunks________________The SWT can support throughput up to approximately 80% of the line speed for speeds from56 or 64 Kbps to T1 rates. The Trunk-PQ can support throughput up to approximately 70%of the line speed for T1 rates and 80% of the line speed for 56 Kbps or 64 Kbps.

The SWT can support up to 506 user channels.

If the Trunk-PQ is configured in a node without CIR traffic administered, 2038 user channelsare supported. If the Trunk-PQ is configured in a node that is administered for CIR traffic,502 user channels are supported.

The Trunk-PQ can connect to only BNS-2000 Release 2.0 or BNS-2000 VCS nodes. TheSWT can connect to any release of BNS-2000 or BNS-2000 VCS nodes.

SAM Links and Trunks

When using the SAMDL in the SAM16 or SAM64, consider the following points. (For aSAM16, the trunk module is an integrated part of the SAM16. The integrated trunk functions asa SAMDL when the SAM16 is administered for a dual link connection.)

The SAMDL is compatible only with a SAMML that is administered to support a dual link.

The facilities for dual links can use different paths between the SAM16 or SAM64 and thenode. However, the lengths of the two paths must not differ by more than 10,000 miles(16,000 kilometers). This distance limit is based on a time limit and is derived from anassumed propagation delay of .01 milliseconds per mile. The latency, or end-to-end delay, foreach path is the total length of time required for a packet to travel from the SAM to the node.The latency for each path is 100 milliseconds. If the difference between the latencies for thetwo paths exceeds 100 milliseconds, packets may arrive out of order.

The data service unit (DSU) used for dual link connections is allowed to use no more than 3.2kHz for all data and control information signaling, unless dual links are routed through privateline facilities between the SAM16 or SAM64 and the backbone network.

The DSUs must support a switched carrier option.

The DSUs must have a latency less than 20 milliseconds. All DSUs used for a dual link musthave the same latency.

To enable load sharing, endpoints must be quiescent (not transmitting or receiving data) for atleast 150 milliseconds every few minutes, implying a poll rate for synchronous service of notmore than six polls per second.

To prevent data underruns, all SAM endpoints that have calls routed over a SAMDL must beadministered for the maximum pipelining buildout value (254). (Pipelining is a process inwhich the interface module transmits a block of data before it receives a complete message orframe from the sending endpoint. The number of bytes accumulated before the module startsto transmit is called the buildout value.)


Trunks________________Dual links should use diverse facilities; if one facility fails, the other link is not affected. Thedual link can only protect SAM16 and SAM64 users from a facility failure if the links arerouted through separate facilities.

A SAM64 or SAM504 can be connected to a BNS-2000 or BNS-2000 VCS node via Trunk-HSfor optical fiber, or Trunk-T1 for T1 carrier. A DDS connection, terminating in a SAMSLmodule at each end, is available for connection of the SAM64 or SAM504 to a BNS-2000 orBNS-2000 VCS node.

Application and Service Specific Traffic

Session maintenance and SMDS traffic have special design considerations:

Session Maintenance detects a trunk failure and makes use of spare capacity of trunks in use,taking advantage of other nodes in the network to provide additional transmission paths. Thisfeature enables CONS to continue without interruption, despite the failure of equipment andfacilities in the path of an established connection.

Most existing networks with sufficient bandwidth and internodal connectivity can supportfailure recovery via Session Maintenance without physical modification. Administrators canconfigure previously unused trunk capacity in the network for use as standby trunk capacitythat supports the alternate reroute paths required for Session Maintenance activities.

See the Session Maintenance Guide for instructions on configuring trunks to support sessionmaintenance traffic.

SMDS traffic is explained in detail in the the BNS-2000 SMDS Guide.


Trunks________________Interworking

BNS-2000 and BNS-2000 VCS network nodes allow trunk connections between any two nodesof any type of CONS traffic, as long as compatible trunk modules are used.

The network does not constrain the choice of routes for calls between endpoints on the same ordifferent types of nodes. The routing algorithm may select any trunk that is administered as aroute from one node to another; therefore the transmission path between compatible endpointdevices may originate at any type of node, traverse any type of node, and terminate at any type ofnode. This type of routing restricts addressing in networks containing mixed node types.

For details of the compatibility of internodal trunks and concentrator links, see the product SystemDescription.

TABLE 4-4. Trunk Module Availability and Compatibility

_ _______________________________________________Availability

Trunk_ _________________________

or BNS-2000 BNS-2000 VCSLink Release 5.0 Release 6.0_ ________________________________________________ _______________________________________________

Fiber CONSSFT √ √Trunk-HS √ √_ _______________________________________________

Wire CONSSAMSL √ √SAMML √ √SWT √ √Trunk-T1 √ √Trunk-PQ √ √Trunk-64 √ √_ _______________________________________________

Wire CONS/CLNSTrunk-E3A √Trunk-E3S √Trunk-T3A √Trunk-T3S √_ _______________________________________________

Wire CLNSTrunk-T3I √_ _______________________________________________


Trunks________________Trunk Channels

BNS-2000 VCS nodes interworking with Datakit VCS or ISN nodes require specialconsideration. In Datakit VCS, the number of channels administered includes the number of userand signaling channels; in BNS-2000 VCS, the number of channels administered includes onlythe number of user channels.

When administering a Trunk-DDS between a BNS-2000 VCS node and a Datakit VCS node,the network administrator must specify that the number of channels at the BNS-2000 VCSend is eight less than the number of channels at the Datakit VCS end.

When administering a Trunk-T1 or Trunk-HS between a BNS-2000 VCS T1 node and aDatakit VCS node, the network administrator must specify that the number of channels at theBNS-2000 VCS end is six less than the number of channels at the Datakit VCS end.

When administering a Trunk-T1 between a BNS-2000 or BNS-2000 VCS node and a DatakitVCS node, the network administrator must specify that the number of channels at the DatakitVCS end is six more than the number of channels at the BNS-2000 or BNS-2000 VCS end.

Trunk Active Tests

To prevent calls from being dropped when interworking with a Datakit VCS Generic 3.4 or laternode, the administrator of the BNS-2000 VCS node must specify the same values as those usedon the Datakit VCS end of the internodal trunk for the following parameters:

— number of seconds between trunk active tests

— maximum consecutive failed active tests


Trunks________________Electrical Specifications and Compliances

When planning a network and each node site, the electrical requirements of each trunk modulehoused in a node, concentrator, or multiplexer must be considered. The distance limits of eachinterface standard must also be considered when planning a node site. The following sections andtables provide this information.

Distance Limits and Interface Standards

Distances to end devices such as modems or DSUs depend on the interface type, data rate, andvendor implementation as shown in the following table.

TABLE 4-5. Trunk Distance Limits

_ _____________________________________________________________________________Maximum Maximum

Physical Supporting Data Cable CableInterface Trunk Rate Length LengthStandard Module (bps) in Feet in Meters Remarks_ ______________________________________________________________________________ _____________________________________________________________________________

DS3 Trunk-T3A 44.736 M N/A N/A BNC coaxial cable

Trunk-T3I

Trunk-T3S_ _____________________________________________________________________________E3 Trunk-E3A 34.368 M N/A N/A 75Ω coaxial cable

Trunk-E3S_ _____________________________________________________________________________Fiber SFT 8 M 884 2.91 km

Trunk-HS_ _____________________________________________________________________________G.703/704/706 SWT 2.048 M 820 250 75Ω coaxial_ ___________________________________________

820 250 120Ω cross-sectional of .5mm_ ___________________________________________984 300 120Ω cross-sectional of .6mm_ _____________________________________________________________________________


Trunks________________TABLE 4-5. Trunk Distance Limits (continued)

_ ________________________________________________________________________Maximum Maximum

Physical Supporting Data Cable CableInterface Trunk Rate Length LengthStandard Module (bps) in Feet in Meters Remarks_ _________________________________________________________________________ ________________________________________________________________________RS-232-C SAMDL ≤19.2 K 50 15

SAMML

SAMSL

SWT

Trunk-DDS

Trunk-64_ ________________________________________________________________________RS-422/449 SWT 2 M 20 6.1 Recommended distance for_ _____________________________

Trunk-T1 1.5 M 40 12.2 COASTCOM DSUs_ _____________________________1 M 60 18.3 is 15 feet maximum._ _____________________________

500 K 140 42.7_ _____________________________100 K 800 243.8_ _____________________________

<=56 K 1600 487.7_ ________________________________________________________________________V.35 SAMML 2 M 20 6.1 Recommended distance for_ _____________________________

SAMSL 1.5 M 40 12.2 COASTCOM DSUs_ _____________________________SWT 1 M 60 18.3 is 15 feet maximum._ _____________________________

Trunk-PQ 500 K 140 42.7_ _____________________________Trunk-64 100 K 800 243.8_ _____________________________

Trunk-DDS <=56 K 1600 487.7

Trunk-T1_ ________________________________________________________________________


Trunks________________Electrical Specifications

The following table provides electrical information that is important when selecting a node siteand when populating a node with trunk modules.

TABLE 4-6. Trunk Module and I/O Board Electrical Service Requirements

_ ____________________________________________________________________________Module I/O Typical Current Amps_ ______________________________________

Module Board Board +5 VDC +12 VDC -12 VDC_ _____________________________________________________________________________ ____________________________________________________________________________SAMSL MC1D090A1B AWJ9 5.8 0.040 0.080

AWJ11 5.8 0.040 0.040_ ______________________________________

EAA2_ ____________________________________________________________________________SAMSL-N MC1D142A1 AWJ9 5.8 0.040 0.080

AWJ11 5.8 0.040 0.040_ ____________________________________________________________________________SAMML MC1D091A1 AWJ9 5.8 0.040 0.080

AWJ17 5.8 0.165 0.165_ ____________________________________________________________________________SFT MC1D085A1 AWJ3 5.0 0.0 0.0_ ____________________________________________________________________________SWT TN2092/ AWJ9 4.5 0.040 0.080

TN2092B AWJ10 4.5 0.0 0.0

AWJ11 4.5 0.040 0.080

AWJ33 4.5 0.01 0.0_ ____________________________________________________________________________Trunk-64 MC1D105A1 AWJ9 5.8 0.040 0.080

AWJ11 5.8 0.040 0.040_ ____________________________________________________________________________Trunk-DDS UN221 ED5P08030G1 6.5 0.0 0.0

_ ____________________________________________________

MC5P033A1 ED5P07630G1 6.5 0.060 0.060

ED5P07930G1 6.5 0.060 0.060_ ____________________________________________________________________________Trunk-E3A CMA18 CMC15 9.5 0.0 0.0_ ____________________________________________________________________________Trunk-E3S CMA13 CMC13B 9.5 0.0 0.0_ ____________________________________________________________________________Trunk-HS TN1010 AWJ2 5.8 0.0 0.0_ ____________________________________________________________________________Trunk-PQ MC1D152A1 AWJ24 4.3 0.035 0.135_ ____________________________________________________________________________Trunk-T1 TN1015 AWJ4 4.8 0.075 0.085_ ____________________________________________________________________________Trunk-T3A CMA18 CMC16 9.5 0.0 0.0_ ____________________________________________________________________________Trunk-T3I CMA14 (egress) CMC6B (egress) 15.5 0.0 0.0

CMA16 (ingress) CMC14 (ingress)_ ____________________________________________________________________________Trunk-T3S CMA13 CMC6B 9.5 0 0_ ____________________________________________________________________________


Trunks________________Electrical/Mechanical Connection Standard Compliances

The following table indicates trunk module compliance to connection standards.

TABLE 4-7. Electrical/Mechanical Connection Standard Compliances

_ ___________________________________________________________________________Connection Standard_ ___________________________________________________

G.703/Trunk ST G.704/ RS-422/Module DS3 E3 Fiber G.706 RS-232-C RS-449 V.35_ ____________________________________________________________________________ ___________________________________________________________________________SAMDL √_ ___________________________________________________________________________SAMML √ √_ ___________________________________________________________________________SAMSL √ √_ ___________________________________________________________________________SFT √_ ___________________________________________________________________________SWT √ √ √ √_ ___________________________________________________________________________Trunk-DDS √ √_ ___________________________________________________________________________Trunk-E3A √_ ___________________________________________________________________________Trunk-E3S √_ ___________________________________________________________________________Trunk-HS √_ ___________________________________________________________________________Trunk-PQ √_ ___________________________________________________________________________Trunk-64 √ √_ ___________________________________________________________________________Trunk-T1 √ √_ ___________________________________________________________________________Trunk-T3A √_ ___________________________________________________________________________Trunk-T3I √_ ___________________________________________________________________________Trunk-T3S √_ ___________________________________________________________________________


________________Interface Modules

Interface Module Types 5-3Interface Module Limits 5-4

General Interface Module Design Issues 5-12Grade of Service 5-12Flow Control 5-13Module Software Download 5-13Port and Device Measurements 5-14Ports versus Modules 5-14

Specific Interface Module Design Issues 5-14

AI 5-15AI-T3 Module 5-16

CPM 5-19

CPY1 (SAM16) 5-19

DKAP 5-20

FRM 5-21Configuration Options 5-21Performance Issues 5-28Engineering Checklist 5-32

FRM-M2 5-34Addressing 5-34Interworking 5-34Configurable Options 5-35Performance Issues 5-44Engineering Checklist 5-49

GAR 5-49

LPM 5-50Physical Ethernet LAN Ports 5-50Virtual Frame Relay Ports 5-50DLCIs, PVCs, and Channels 5-50DLCI Data Rates 5-51PVC Addressing 5-51Maximum Transmission Unit 5-52


________________Window Size 5-52Congestion Management 5-52Maximum Aggregate CIR from Remote Devices 5-53Bc Size 5-53Be Size 5-53Discard Eligibility Bits 5-54Discarded Frames 5-54Congestion Management Over Time 5-54Port Screening Filters 5-54IP Routing 5-54Alternate IP Routing 5-55IP Addressing 5-55

MSM 5-57

SYNC8 5-58

TERM32 5-60

TSM8 5-61

TSM-T1 5-62Network Load 5-62Minimum Number of Modules Needed 5-62Number of Ports 5-64Backbone Trunk Speeds 5-64Backbone Trunk Modules 5-64Port Configuration Options 5-65TSM-T1 Network Performance 5-72

TY 5-82

X.25 5-84

X.25P 5-85Configuration Options 5-86Module Throughput 5-90

X.75 5-97Configuration Options for X.75 Service 5-97

Interworking 5-102

Electrical Specifications 5-108


________________Interface Modules

This chapter provides all physical and hardware-related details on interface modules. It includesgeneral design issues that affect all modules and specific design issues that affect a particularmodule. Module electrical requirements and interworking information are also included. Otheraspects of interface modules are treated elsewhere, as follows:

Module placement guidelines are explained fully in the Node chapter.

Module identifiers, such as addresses and groups, are explained in the Addresses and Groupschapter.

Methods of network security are explained in the Security chapter.

Spare parts information is provided in Appendix A.

In addition, the BNS-2000 System Description contains a complete explanation of each supportedinterface module. Module references for the specific interface modules contain more details oninstallation, cabling, and administration.

Interface Module Types

The choice of interface module depends on the services that end users need to perform their dailytasks, the connected end devices that users must rely on to access network services, and thenetwork services to which end users, or groups of end users, must have access.

The following table lists the categories of services available, the interface modules that supportthe services available, and the Data Networking Products that support the services and modules.When choosing a particular service, keep in mind the following caveats:

Connectionless transport services (SMDS via the AI modules) must be routed only betweenBNS-2000 nodes by Series M2 trunk modules such as the Trunk-T3S and/or Trunk-E3S.

Several interface modules provide similar services. Evaluate customer requirements todetermine which module best suits the needs of the customer and network provider.

The number of port connections and user channels available differ among interface modulesthat offer basic asynchronous and synchronous services.


Interface Modules________________TABLE 5-1. Interface Module Services

_ ______________________________________________________________Supporting Data Networking Product

Interface_ ________________________

Service Module BNS-2000 BNS-2000 VCS_ _______________________________________________________________ ______________________________________________________________Asynchronous MSM √ √

TY12 √ √TY6 √ √CPY1 (SAM16) √ √TERM32 (SAM64/504) √ √TSM8 √ √_ ______________________________________________________________

Customer Programmable

Applications Processing: DKAP √ √_ ______________________________________________________________LAN Interconnect FRM √ √

FRM-M2 √LPM √ √_ ______________________________________________________________

Multiplexed Host CPM-HS √ √_ ______________________________________________________________SMDS AI-E1 √

AI-E3 √AI-T1 √AI-T3 √AI-T3P √GAR √_ ______________________________________________________________

Special Purpose: E2A √ √OS Services SLM √ √_ ______________________________________________________________Standards: X.25 √ √PDN/PSPDN Access X.25P √ √

X.75 √ √_ ______________________________________________________________Switched Bisynchronous SYNC8 (bsc3270) √ √_ ______________________________________________________________Synchronous TSM8 √ √

TSM-T1 √ √CPY1 (SAM16) √ √TERM32 (SAM64/504) √ √_ ______________________________________________________________

Interface Module LimitsWhen network services are planned, the limitations imposed upon each interface module arecritical in the design process. Great care must be taken to ensure that the combined load of allmodules in use at any given time does not exceed the node backplane capacity. The followingtables group interface modules by the broad services they support. They explain modulelimitations in terms of the number of ports supported and transmission speeds. In addition, otherservice-specific features—such as flow control and parity for asynchronous modules andprotocols supported for synchronous modules—are provided for comparisons. These factors willprobably determine which module is most appropriate to support a given customer need.


Interface Modules________________TABLE 5-2. Asynchronous Module Characteristics

_ _____________________________________________________________________Number Speed Flow

Module of Ports (bps) Control Remarks_ ______________________________________________________________________ _____________________________________________________________________75 to115.2 K

XON/XOFF,EIA, ornone

Multispeed Module (MSM). Mostappropriate for support ofasynchronous speeds above 19.2 Kbps,but supports the full range of speeds.

MSM 12

_ _____________________________________________________________________300 to19.2 K


Basic asynchronous interface supportfor most common speeds up to 19.2Kbps. When maximum ports areconfigured, ports running at 19.2 Kbpsmust have flow control set to avoiddata loss.

TY12 12

_ _____________________________________________________________________75 to19.2 K

XON/XOFF Basic asynchronous interface supportfor most common speeds up to 19.2Kbps. Additional options are availableto support specific applications such asSCCS.

TY6 6

_ _____________________________________________________________________CPY1(SAM16)

75 to19.2 K


Basic asynchronous interface supporton SAM16 for most common speeds upto 19.2 Kbps. When maximum portsare configured, ports running at 19.2Kbps must have flow control set toavoid data loss.

16

_ _____________________________________________________________________75 to19.2 K


Basic asynchronous interface supporton SAM64 and SAM504 for mostcommon speeds up to 19.2 Kbps.When maximum ports are configured,ports running at 19.2 Kbps must haveflow control set to avoid data loss.

TERM32 32

_ _____________________________________________________________________75 to19.2 K


Primarily a synchronous interfacemodule, but supports asynchronousservice for calls to PDDs only.

TSM8 8

_ _____________________________________________________________________


Interface Modules________________TABLE 5-3. Customer Programmable Module_ ____________________________________________________________________________

Module Number ofChannels Remarks_ _____________________________________________________________________________ ____________________________________________________________________________

507; 63 channelsets

Application processor module used to provide customized protocolsupport within the node. Cannot be used without customizedprogramming.

DKAP

_ ____________________________________________________________________________

TABLE 5-4. LAN Interconnect Module Characteristics_ _____________________________________________________________________________________Number Number

of of SpeedModule Ports Channels (bps) Protocols Remarks_ ______________________________________________________________________________________ _____________________________________________________________________________________

6 physical;up to 24virtual

56, 64 K to1.544 M(in 64 Kincrements)

ANSI T1.617,T1.618, T1.606,CCITT Q.922,Q.933, andFRF.1 FRF.2

Multiport channelizedT1/E1 frame relay interfacethat supports extendedaddressing. Resides inSeries M2 Shelves only.

FRM-M2 (ChT1) 2000

__________________________________________________6 physical;up to 31virtual

64 K to2.048 M(in 64 Kincrements)

FRM-M2 (ChE1) 2000

_ _____________________________________________________________________________________9.6 K to2.048 M

ANSI T1.617,T1.618, T1.606,CCITT Q.922,Q.933, andFRF.1 FRF.2

Basic frame relay interfaceat speeds up to T1/E1.Both multiple ports andchannelized interfaces aresupported depending on thechoice of I/O board.Resides in a Series M1Shelf or modular cabinet.

FRM (V.35) 4 507


56, 64 K to1.544 M(in 64 Kincrements)

FRM (ChT1) 507


64 K to2.048 M(in 64 Kincrements)

FRM (ChE1) 507

_ _____________________________________________________________________________________up to 1.544 M Ethernet; 802.3

MACEthernet LAN interfacemodule; supports up to 2(full duplex) LAN portsand up to 27 virtual framerelay ports with up to 507virtual circuits. Usesstandard TCP/IP andEthernet cabling. Residesin a Series M1 Shelf ormodular cabinet.

LPM 2 507

_ _____________________________________________________________________________________


Interface Modules________________TABLE 5-5. Multiplexed Host Characteristics

_ ________________________________________________________________________Number of Distance

Module User Channels Limit Remarks_ _________________________________________________________________________ ________________________________________________________________________CPM-HS 509 up to Supports high-speed, multiplexed connections

3250 feet over fiber optic links for currently supported

Lucent Technologies host computer systems and the host

computer systems of other vendors.

Distance limits differ depend on host type._ ________________________________________________________________________

TABLE 5-6. SMDS Access Interface (AI) Module Characteristics_ ____________________________________________________________________________

Numberof Speed

Module Ports (bps) Remarks_ _____________________________________________________________________________ ____________________________________________________________________________Standard connectionless SMDS service interface at speeds up toT1/E1. Protocols: DQDB and PLCP. Installed in Series M2 Shelfonly.

AI-T1 4 1.544 M

_ ____________________________AI-E1 3 2.048 M_ ____________________________________________________________________________

Standard connectionless SMDS service interface at speeds up toT3/E3. Supports performance up to Class 4 (25 Mbps). StandardProtocols: DQDB and PLCP. Installed in Series M2 Shelf only.

AI-T3 1 44.736 M

_ ____________________________AI-E3 1 34 M_ ____________________________________________________________________________

1 Enhanced connectionless SMDS service interface at speeds up toT3/E3. Supports performance up to Class 5 (34 Mbps). Two boardmodule; installed in Series M2 Shelf only.

AI-T3P 44.736 M

_ ____________________________________________________________________________Provides the capabilities of a GAA. Needed only in SMDS networksserving as a GAA for group addresses. Up to 8 GARs per agentnetwork are allowed. Installed in Series M2 Shelf only; shelfnumbers 1, 2, or 3; cannot be installed in shelf numbers 6 or 7.

GAR N/A N/A

_ ____________________________________________________________________________


Interface Modules________________TABLE 5-7. Special Module Characteristics_ ______________________________________________________________________________

Number SpeedModule of Ports (bps) Protocols Remarks_ _______________________________________________________________________________ ______________________________________________________________________________

1.2 K E2A Special purpose modulededicated to telemetryservice for SCCS/TNM.

E2A 4

_ ______________________________________________________________________________2.4 to 9.6 K Two-board, special-

purpose modulededicated to BX.25service.

SLM 4 BX.25 Issue 2

_ ______________________________________________________________________________

TABLE 5-8. Standards Module Characteristics

_ ______________________________________________________________________________Number Speed Number of

Module of Ports (bps) Channels Protocols Remarks_ _______________________________________________________________________________ ______________________________________________________________________________1.2, 2.4, 4.8, 9.6,19.2, 48, 56, 64K

Up to 100 X.25 (CCITT1988).Supports X.3,X.28, X.29PAD service.

Basic X.25 interface forspeeds up to 64 Kbps. At48 Kbps and higher, onlyone port is supported.

X.25 4

_ ______________________________________________________________________________Up to 507 X.25 (CCITT

1988). SupportsX.3, X.28,X.29 PADservice.

Enhanced X.25 interfacefor speeds up to 2.048 Mwith up to 8 ports at 19.2Kbps; up to 4 ports at128 Kbps; or one port atthe T1/E1 rate.

X.25P 4 V.35 9.6 K to 2.048 M

1.2 to 19.2 KDTE, externalclocking only.

-or-

1.2, 2.4, 4.8, 9.6,14.4, 19.2 KDCE, internalclocking.

8 RS-232-C

_ ______________________________________________________________________________56 K, 64 K,T1, E1

Up to 507 X.75 (CCITT1988).Supports X.3,X.28, X.29PAD service.

Standard X.75 interfaceat speeds up to T1/E1.

X.75 4

_ ______________________________________________________________________________


Interface Modules________________TABLE 5-9. Synchronous Module Characteristics_ __________________________________________________________________________________

Number Speed Number ofModule of Ports (bps) Channels Protocols Remarks_ ___________________________________________________________________________________ __________________________________________________________________________________

2.4, 4.8, 9.6,19.2, 48, 56,64 K

BSC,Burroughs/NCRPoll/Select,DDCMP, HDLC,SDLC, UNISCOPE

Basic synchronousinterface module forspeeds up to 64 Kbps.Only DTE version can beused for 48 Kbps andhigher. DDCMP issupported up to 56 Kbps.At 56 Kbps, pipeliningshould be disabled. At48 Kbps and higher, oneport is supported.

TSM8 8 150

_ __________________________________________________________________________________4 9.6 K to

2.048 MHDLC, SDLC Basic synchronous

interface module forspeeds up to T1/E1.Aggregate modulethroughput is limited toT1 speeds.

TSM-T1 200

_ __________________________________________________________________________________110 and .3,1.2, 2.4, 4.8,9.6, 19.2 K, orDTE w/ext.clock

BSC, SDLC,HDLC, DDCMP,Burroughs/NCRPoll/Select,UNISCOPE

Basic synchronousinterface support onSAM16 for speeds up to19.2 Kbps.

CPY1 (SAM16) 16 16

_ __________________________________________________________________________________110 and .3,1.2, 2.4, 4.8,9.6 K, or DTEw/ext. clock

BSC, SDLC,HDLC, DDCMP,Burroughs/NCRPoll/Select,UNISCOPE

Basic synchronousinterface support onSAM64 and SAM504supporting speeds up to9.6 Kbps.

TERM32 32 32

_ __________________________________________________________________________________2.4 K to 56 K Support for switched

3270 service. At 48 Kbpsand higher, one port issupported. Supports upto 8 ports per moduledepending on speed andtraffic. Each portsupports up to 32 CUs;each CU supports up to32 devices, with amaximum of 128 devicesper module.

SYNC8 8 128 Switched 3270BSC

_ __________________________________________________________________________________


Interface Modules________________The following table shows the interface module and its appropriate module and I/O distributionboards. When appropriate, the number of ports and the type of connection they provide aresupplied.

TABLE 5-10. Interface Module and I/O Board Port Connections

_ ____________________________________________________________________________Number

Module I/O of Port Connections/Module Board Board Slots Remarks_ _____________________________________________________________________________ ____________________________________________________________________________

AI-E1 CMA5 CMC8 1 3 E1_ ____________________________________________________________________________AI-E3 CMA11B CMC13 1 1 E3_ ____________________________________________________________________________AI-T1 CMA5 CMC5/CMC5B 1 4 T1_ ____________________________________________________________________________AI-T3 CMA11B CMC6 1 1 DS3_ ____________________________________________________________________________AI-T3P CMA17 CMC14 2 1 DS3

CMC6B_ ____________________________________________________________________________CPY1 (SAM16) N/A Integrated 1 16 (SAM16) V.35 or RS-232-C_ ____________________________________________________________________________CPM-HS TN1009 AWJ2 1 Optical fiber up to 3 km_ ____________________________________________________________________________DKAP MC2P023A1 None 1 No external connections_ ____________________________________________________________________________E2A TN1012 ED5P074-30,G1 1 E2A telemetry for SCCS/TNM_ ____________________________________________________________________________FRM MC1D143A1 AWJ24 1 4 V.35 DTE_ ________________________________________________

CSD1 1 1 direct T1 interface (channelized)_ ________________________________________________CSD2 1 1 75-ohm E1 interface (channelized)_ ________________________________________________CSD3 1 1 120-ohm E1 interface (channelized)_ ____________________________________________________________________________

FRM-M2 CTG1 CMC20 1 6 direct T1 interface (channelized)_ ________________________________________________CMC18 1 6 75-ohm E1 interface (channelized)_ ________________________________________________CMC19 1 6 120-ohm E1 interface (channelized)_ ____________________________________________________________________________


Interface Modules________________TABLE 5-10. Interface Module and I/O Board Port Connections (continued)_ ____________________________________________________________________________

NumberModule I/O of Port Connections/

Module Board Board Slots Remarks_ _____________________________________________________________________________ ____________________________________________________________________________GAR CMA15 CMC14 1 No external connection_ ____________________________________________________________________________LPM TN2229 CSD6 1 2 RJ45 connections (10BASE-T)_ ____________________________________________________________________________MSM TN2111B AWJ4 1 12 RS-232-C DTE_ ____________________________________________________________________________SLM UN221 ED5P077-30,G1 2 BX.25 for TNM, TDMS, etc.

MC5P025A1 ED5P080-30,G1_ ____________________________________________________________________________SYNC8 MC1D089A1 AWJ5 1 1 V.35 DTE and 3 RS-232-C DCE

(bsc3270)_ ________________________________________________

AWJ6 1 1 V.35 DTE and 3 RS-232-C DTE_ ________________________________________________AWJ17 1 8 RS-232-C DTE_ ________________________________________________AWJ18 1 8 RS-232-C DCE_ ____________________________________________________________________________

TERM32 UN315 ED2P466-30,G1 1 32 RS-232-C DTE_ ____________________________________________________________________________TSM8 MC1D088A1 AWJ5 1 1 V.35 DTE and 3 RS-232-C DCE_ ________________________________________________

AWJ6 1 1 V.35 DTE and 3 RS-232-C DTE_ ________________________________________________AWJ7 1 8 RS-232-C DTE with NRZI_ ________________________________________________AWJ8 1 8 RS-232-C DCE with NRZI_ ________________________________________________AWJ17 1 8 RS-232-C DTE_ ________________________________________________AWJ18 1 8 RS-232-C DCE_ ____________________________________________________________________________

TSM-T1 MC1D149A1 AWJ24 1 4 V.35 DTE_ ____________________________________________________________________________TY6 TN1006 ED5P066-30,G1 1 6 RS-232-C DTE_ ____________________________________________________________________________TY12 TN2157/TN1011C AWJ4 1 12 RS-232-C DTE_ ____________________________________________________________________________X.25 TN2094 AWJ5 1 1 V.35 DTE and 3 RS-232-C DCE_ ________________________________________________

AWJ6 1 1 V.35 DTE and 3 RS-232-C DTE_ ________________________________________________AWJ17 1 4 RS-232-C DTE_ ________________________________________________AWJ18 1 4 RS-232-C DCE_ ____________________________________________________________________________

X.25P MC1D153A1 AWJ24 1 4 V.35 DTE_ ________________________________________________CSD4 1 8 RS-232-C DTE/DCE_ ____________________________________________________________________________

X.75 MC1D151A1 AWJ24 1 4 V.35 DTE_ ____________________________________________________________________________


Interface Modules________________General Interface Module Design Issues

The interface module planning process includes consideration of the features and demands thatcertain modules and their connected end devices make on network resources. This sectiondescribes some more significant design issues that may affect the overall planning for interfacemodules:

Grade of service (GOS) — error detection and recovery properties of the internalcommunication protocol used between interface modules withing the network.

Flow control — interface module control of data flow from end devices.

Module software download — download of module software during module reset or systeminitialization.

Port and device measurements — the effect of measurement collection on load andperformance.

Ports versus modules — general guidelines on the use of spare ports versus the addition ofinterface modules to the existing configuration.

Grade of Service

Modules internal to a Data Networking Products node communicate via an internalcommunications protocol with a grade of service (GOS). The GOS is the level of supportprovided for flow control, error detection, and correction. All interface modules operating in aCONS environment can receive traffic at all GOS levels. However, modules generally transmit atone or two GOS levels. A description of the five GOS levels is shown in the following table.

TABLE 5-11. GOS Levels

_ _________________________________________________________Level Description_ __________________________________________________________ _________________________________________________________GOS1 No flow control; no error control._ _________________________________________________________GOS2 Flow control; no error control._ _________________________________________________________

No flow control or retransmission; provides error detection. GOS3_ _________________________________________________________Flow control and error detection are provided; noretransmission of corrupted or missing blocks.

GOS4

_ _________________________________________________________Flow control; error detection; retransmission. GOS5_ _________________________________________________________


Interface Modules________________Flow Control

The Data Networking Products nodes can switch data with minimum delay and move it throughthe network as fast as possible with minimum buffering. Flow control, determined by the GOS,is used to manage congestion by limiting the amount of data that can build up within a virtualcircuit.

The particular node specifies, for each virtual circuit, a limit to the volume of data that can be intransit at any one moment. The data is not permitted to occupy more than a predeterminedamount of queue space; the excess data is stored for transmission in a buffer.

Node flow control features permit the network administrator to set flow control using a variety ofoptions. For asynchronous devices, the network nodes support flow control through software(XON/XOFF) or hardware (RTS/CTS) options. In addition, network nodes can flow control thedevices, be controlled by them, or both. Administrators can also select no flow control.

To avoid data loss, the network administrator should select a flow control option whenconfiguring module ports. Flow control available with each network node:

limits the amount of data in transit on a virtual circuit to the internal buffer size and

provides end-to-end flow control with the connecting devices.

To avoid data loss if a flow control option is not selected, the connecting devices must ensure thatthe volume of data in transit in each direction of a virtual circuit is less than the buffer limit forthat type of interface module.

Module Software Download

Module software downloads affect the use of network resources within a node. Many interfacemodules require their software to be downloaded when the module is rebooted or when the nodesoftware release is upgraded. Depending on the number of modules involved, the load on theControl Computer and the time to complete the download can be significant. In addition, thedownload process consumes significant bandwidth on links to concentrators.

During a cold boot of the node, modules are downloaded and activated in sequence, starting withthe modules residing in the lowest addresses and ending with the modules residing in the highestaddresses. Activation of receiving (destination) modules before the activation of originatingmodules avoids the possibility of poor route selection and other anomalous behavior. Therefore,modules containing terminating endpoints (modules associated with receiving groups such asmultiplexed host computer interface modules) should be placed into lower-numbered addresses,while originating endpoints (modules associated with originating groups such as terminals)should be placed into higher-numbered addresses.


Interface Modules________________Port and Device Measurements

Measurements on ports and connected end devices may have an effect on the use of networkresources. On many modules, the port or channel to which each connected end device is attachedmust be sampled for traffic measurements. The demands that connected end devices make on anetwork can be evaluated using these calculations of busy-hour activity each port type:

the average amount of traffic generated per port, which should be based on continuous activity

the average number of logical channels (virtual circuits) occupied per port, which should be afraction of that port’s maximum virtual circuit capacity.

the average channel occupancy per port for each site in the network.

This information can be obtained by actual data or by estimating. Needless to say, actual datashould be used whenever possible because the overall network design will only be as good as theinformation used in the initial calculations.

Ports versus Modules

Before adding additional modules to accommodate end user services, ports on existing modulesshould be used. Using existing ports is more economical. Unused module ports consumedatabase space and reduce the space available for ports on other modules. Such a configurationcan result in node underutilization.

However, if a few connected end devices are close enough to connect directly to a module or if afew devices are depleting module bandwidth, it is more prudent to add a module to theconfiguration than to use existing module ports.

Specific Interface Module Design Issues

Because many variables affect the performance of any data network, this section cannot coverevery possible detail. Instead, it presents general guidelines to illustrate the relationship of theconfiguration options of certain interface modules and shows how these options affect networkperformance. These general guidelines are presented as recommendations only and should not beconsidered performance guarantees for any actual network.

In addition, all performance measurements that appear were taken under ideal laboratoryconditions without other traffic or noisy trunks. They are included as a starting point for networkplanning, not as an absolute measure of performance.


Interface Modules________________AI

All Access Interface (AI) modules are installed in Series M2 Shelves only and all support DQDBand PLCP protocols. A maximum of 63 AI modules can be supported per node with four portseach.

The AI-T1 and AI-E1 support connectionless data transport for SMDS service at speeds of T1and E1. These modules use the facility clock or the Stratum 4 Clock as their transmit referenceclock source.

The AI-T3 and AI-E3 support connectionless data transport for SMDS service at speeds of T3and E3. SMDS defines several access classes that are used to specify the requested sustainedinformation rate, as shown in the following table.

TABLE 5-12. SMDS Access Class and Sustained Information Rate

_ ________________________________Access Class Sustained Information

Identifier Rate (Mbps)_ _________________________________ ________________________________1 4_ ________________________________2 10_ ________________________________3 16_ ________________________________4 25_ ________________________________5 34_ ________________________________

The AI-T3 and AI-E3 support access classes 1 to 4. The access class is not intended to be (norshould it be used as) a guarantee of end user throughput. Actual end-to-end user throughputdepends on a variety of factors, including the size of the user messages (the L3_PDU), thespecific data traffic pattern, the load on the nodes and trunks in the network path, and the totalload on the AI modules.

The AI-T3P is a two-board module that supports connectionless data transport for SMDS serviceat T3 speeds. The AI-T3P can support access classes 1 to 5. One board is dedicated to ingresstraffic, the other board to egress. This board dedication allows the AI-T3P to support accessclass 5 performance even when handling heavy traffic in both the ingress and egress directionssimultaneously.


Interface Modules________________AI-T3 Module

This section provides DS3 access class requirements and the performance results for an AccessInterface (AI) module residing in a BNS-2000 node configuration. Measurements were collectedfor full duplex (ingress and egress) traffic.

The development of Lucent’s SMDS was based on Bellcore requirements, which specified accessclass requirements at the DS3 rate to accommodate customer’s need and to allow for burstytraffic. Five different classes are provided at the DS3 rate. Each provides a different SustainedInformation Rate (SIR) for user information. The following table shows the different accessclasses and allowable SIR.

TABLE 5-13. Access Class Identifiers and Sustained Information Rates

_ _____________________Access Class SIR

Identifier in Mbps_ ______________________ _____________________1 4_ _____________________2 10_ _____________________3 16_ _____________________4 25_ _____________________5 34_ _____________________

The configuration in which performance measurements were collected consisted of a single nodeconfigured with two AI-T3 and AI-T3P modules that were connected to AU45 load generators. ADual Router Configuration (DRC) was used for the two board AI-T3P module. Each moduleboard was connected to its own AU45: one was for ingress; the other one was for egress. Thisset-up allowed the AI-T3P to perform to full capacity, near Access Class 5, without congestingthe routers.

Performance measurements were taken with the SMDS Billing feature globally activated and thenwith the SMDS Billing feature deactivated. There was no difference in the performance.


Interface Modules________________The following figure shows the measurements collected for full duplex (ingress and egress) trafficunder the conditions previously described.

100

95

90

85

80

75

70

65

60

55

50

45

40

35

30

25

20

15

10

5

1

A1T3 Full Duplex Performance

Number of L2_PDUs

% of Throughput

1 10 20 50 100 200

FIGURE 5-1. AI-T3 Full Duplex Performance

Dashed line indicates AI-T3 Measurements.

Dotted line indicates AI-T3 Measurements. When the SMDS billing was globally activated and then deactivated, performance

differences did not ocurr.

Solid line indicates AI-T3P Measurements. Dual router configuration used at full load capacity, which was close to Class 5.


Interface Modules________________The following table summerizes the data collected for full duplex testing._ ____________________________________________________________________________

Number of L2 Inter-arrival LOADCF smdsget Performanceper L3_PDU Delay in usec N L2_PDUS M L2_PDUs M/96000

n t_ _____________________________________________________________________________ ____________________________________________________________________________1 31 32258 17200 17.7_ ____________________________________________________________________________2 70 28571 20000 20.8_ ____________________________________________________________________________3 83 36144 24600 25.625_ ____________________________________________________________________________4 126 31746 26200 27.29_ ____________________________________________________________________________5 139 35971 29600 30.8_ ____________________________________________________________________________8 200 40000 34200 35.625_ ____________________________________________________________________________

10 252 39682 35400 36.875_ ____________________________________________________________________________12 283 42402 36800 38.34_ ____________________________________________________________________________16 380 42105 38300 39.895_ ____________________________________________________________________________20 470 42553 39500 41.14_ ____________________________________________________________________________25 585 42735 40000 41.67_ ____________________________________________________________________________30 700 42857 40400 42.08_ ____________________________________________________________________________40 920 43478 41500 43.2_ ____________________________________________________________________________50 1140 43859 42200 43.9_ ____________________________________________________________________________60 1370 44117 42600 44.37_ ____________________________________________________________________________80 1810 44198 42800 44.58_ ____________________________________________________________________________

100 2250 44444 43000 44.79_ ____________________________________________________________________________120 2700 44444 43200 45.0_ ____________________________________________________________________________160 3590 44568 43600 45.4_ ____________________________________________________________________________200 4480 44642 43720 45.54_ ____________________________________________________________________________210 - - - -_ ____________________________________________________________________________


Interface Modules________________CPM

When connecting an asynchronous host with more than 50 channels, consider using the ComputerPort Module-High Speed (CPM-HS) rather than an asynchronous module interface, like the TY12module. For a substantial number of channels, the multiplexed host interface may be moreeconomical, and its channels consume fewer control channels and switch memory thanasynchronous ports.

If possible, locate multiplexed host interfaces in nodes rather than in MPCs. They consume fewerresources in the node.

Full interworking is supported between multiplexed host interfaces across all BNS-2000 VCS andBNS-2000 releases. These multiplexed host interfaces interwork fully with other asynchronousmodules, LAN clients connected through LAN gateways and servers, and the X.25, X.25P, andX.75 asynchronous PAD service.

CPY1 (SAM16)

The CPY1 resides only in the SAM16. When configured for asynchronous service, the CPY1’s16 full-duplex ports can run at speeds from 75 bps up to 19200 bps. The CPY1 also supportsautobaud, or automatic adjustment to the speed of the connected endpoint, at speeds from 75 bpsto 19200 bps. The total throughput of the CPY1 for asynchronous communication is about 100Kbps.

Each port can be configured for 19.2 Kbps full-duplex. However, the total throughput isconstrained by the capacity of the processor capacity and the trunk that links the CPY1 to thenode.

The CPY1 asynchronous interface does not have the capacity to transmit data at the aggregate ofthe configurable port speeds over extended periods of time. To meet the needs of devicesrequiring high sustained throughput, it may be necessary to reduce the number of active CPY1ports.

Despite this constraint, the CPY1 is designed to minimize errors during overload. Each CPY1port has 3683 bytes of buffer available to accept data from a connected device. Once data isaccepted, the GOS5 transmitter transmits it across the network. As long as the buffer does notoverflow, data is not lost.

Asynchronous ports can be configured to support XON/XOFF or EIA flow control. Thus, theCPY1 interface buffers are protected provided the external devices support one of these flowcontrol mechanisms.

The CPY1 supports a continuous full-duplex flow of data on 16 ports simultaneously at 9.6 Kbpswithout flow control. It supports a continuous full-duplex flow of data on all ports up to 19.2Kbps with flow control. For half-duplex communications, it supports all ports up to 9.6 Kbpswithout flow control and all ports up to 19.2 Kbps with flow control enabled.


Interface Modules________________CPY1 ports configured for asynchronous transport and running at speeds of less than 19.2 Kbpscan use any combination of flow control and 1 or 2 stop bits. Flow control must be enabled forspeeds equal to 19.2 Kbps.

For synchronous transmission, the CPY1 can serve as the interface between the protocol of theexternal device and the internal packet protocol, providing buffering and data flow control. Iteffectively transmits frames in half-duplex or full-duplex environments where thecommunications lines operate at an occupancy of 95% at 19.2 Kbps. If a synchronous devicecontinuously streams data into a port, receiver overruns can occur as the module runs out ofbuffers. If overruns occur, the protocol error recovery procedures recover lost data. Follow theguidelines specified in Concentrators and Multiplexers to set flow control mechanisms withinthe protocols to limit the amount of data sent to the CPY1 and thus eliminate buffer overruns.

DKAP

The DKAP is a plug-in module that includes a processor, 64 KB of ROM, 2 MB of RAM, and aninterface to the node backplane. The DKAP is not equipped with an I/O distribution board.Throughput for the DKAP is about 80 Kbps.

If nodes are running customized applications on the DKAP, the network administrator mustrecompile them using the portable development environment (PDE) software. When upgradingto the environment of the current software release, consult the PDE Programmer’s Guide foradvice on recompiling.

Specifically, if upgrading to BNS-2000 VCS Release 6.0 or higher, or to any BNS-2000 Release2.0 or higher, recompilation of the DKAP application is needed because the number of channelsets available on the DKAP has been increased from 20 (MAXACS) to 63 (NEWMAXACS).

All references to MAXACS should be replaced with NEWMAXACS in the DKAP applicationand the application should be recompiled with the PDE release that is compatible with the nodesoftware. This change and the recompilation avoids possible incompatibility problems if achannel set between 21 and 63 is inadvertently configured and the DKAP software cannot supportit. Also, when replacing MAXACS with NEWMAXACS, look for any instances where thenumber 20 may have been used in the application. This may point out instances of MAXACS.

The PDE for the DKAP can fully interwork with all releases. Complete interworking isdependent on the specific applications that reside on the DKAP.


Interface Modules________________FRM

The node supports the data link connection identifier (DLCI) for permanent virtual circuits(PVCs) through the Frame Relay Module (FRM). Each PVC requires two DLCIs. When a DLCIis administered, the Control Computer associates it with a channel number in the FRM. A PVCcall is set up to associate one port and DLCI (where the PVC originates), with a second port andDLCI (the destination of the PVC) in the network.

The frame relay address field uses two octets to carry the DLCI. Some DLCIs are reserved forother functions, leaving 992 distinct DLCI numbers (from 16 to 1007) available for PVC use ateach FRM port. DLCI numbers 1019 to 1022 are available for multicast DLCIs only. Inoperation, each module supports a maximum of 507 DLCIs. If extended measurements areadministered, each module supports a maximum of 300 DLCIs. Any DLCI numbers can bechosen from among those available; they do not have to form contiguous sequences.

The format for a frame relay address in a node or MPC is:

Mnemonic address: [network/area/exchange/]local.[concentrator/]module.port.DLCI

X.121 address: [DNIC/SR/SA/EPN].[concentrator/]module.port.DLCI

In these address formats, port can be the port number for an FRM (V.35) or the virtual portnumber for an FRM (ChT1) or an FRM (ChE1). To interwork with the FRM-M2, the call shouldoriginate on the FRM-M2.

Configuration Options

The FRM provides the interface to support local area network (LAN) Interconnect through awide-area network (WAN). To reach the desired levels of service performance, severalconfiguration options must be balanced.

Module Throughput

The maximum module throughput for the FRM depends on the frame size for the data beingtransmitted. Frame size refers to the size of the information field in the frame relay framereceived from the access device. The following table shows the aggregate total throughput forvarious frame sizes. For a given frame size, the total aggregate throughput for all active portsshould not exceed the total module aggregate throughput.


Interface Modules________________The FRM (ChT1) supports up to 24 virtual ports which can be configured for a total aggregatespeed of 1536 Kbps. The FRM (ChE1) supports up to 31 virtual ports which can be configuredfor a total aggregate speed of 2048 Kbps.

All four FRM (V.35) ports can be configured at T1 or E1 speeds. The actual module throughput,however, cannot exceed the number shown in the following table.

TABLE 5-14. FRM Throughput and Frame Size

_ _______________________________________Frame Size Total Aggregate Bi-directional

Module Throughput (in Kbps)_ _______________________________________FRM (V.35) (E1 rate)_ _______________________________________

64 900_ _______________________________________262 2800_ _______________________________________576 3700_ _______________________________________

1500 (or more)

4000_ _______________________________________FRM (ChT1)_ _______________________________________

64 880_ _______________________________________262 2400_ _______________________________________576 (or more)

3072_ _______________________________________FRM (ChE1)_ _______________________________________

64 870_ _______________________________________576 3300_ _______________________________________

1200 3725_ _______________________________________2048 (or more) 3890_ _______________________________________

To determine whether traffic through the FRM is exceeding the supported aggregate modulethroughput, use the dmeas command. If any value for AVERAGE MAIN UTIL , CURRENT MAINUTIL , PEAK MAIN UTIL , AVERAGE I/O BD UTIL , CURRENT I/O BD UTIL , or PEAKI/O BD UTIL exceeds 95%, the FRM is congested and module traffic should be reduced.

Number of PVCs

The FRM can support 507 virtual circuits; each virtual circuit maps to a pair of DLCIs. Ifextended measurements are administered, the FRM can support 300 virtual circuits. Thus, agiven frame relay endpoint can communicate with up to 507 other endpoints. The total numberof frame relay endpoints in the network can, however, be much greater than 507. A virtualcircuit is administered as a predefined destination (PDD); each PDD corresponds to one PVC.


Interface Modules________________DLCI Data Rates

The FRM supports three optional parameters to control the data rates for DLCIs:

committed information rate (CIR)

committed Burst size (Bc)

excess Burst size (Be)

The relationship of these parameters is explained in the following sections on these parameters.A DLCI can be configured as non-CIR; in that case these parameters do not apply.

In related options, the FRM supports throughput tuning for end-to-end flow control on eachDLCI, and XON/XOFF flow control on each FRM port using local management interface (LMI)for PVC management. For information about these options, see the Window Size andXON/XOFF Flow Control sections.

XON/XOFF Flow Control

The FRM can be configured to use the LMI for PVC management. This enables the FRM torespond to buffer congestion as follows:

When the FRM becomes congested, it sends an XOFF to the access device that is transmittingacross the interface. The XOFF is indicated by setting the R-bit in a PVC status message.

When the FRM is no longer congested, it sends an XON. The XON is indicated by clearingthe R-bit in a PVC status message.

The FRM uses the same criteria to determine congestion for sending XONs and XOFFs as it doesfor sending Forward Explicit Congestion Notification (FECN) and Backward Explicit CongestionNotification (BECN) messages.

Maximum Length of Information Field

The frame relay standard enables the network administrator to set a limit for the maximumnumber of octets in the information field of each frame by configuring the MAXIMUM FRAMESIZE parameter. A separate limit may be specified for each port, ranging in size from 262 to4096 octets. The default is 4096. If a frame is received that is larger than the maximum sizeallowed, it is discarded and an alarm is sent to the node console.

Recommendation. To optimize the buffering over intermediate trunks, configure the smallestmaximum frame size that meets the needs of the application.


Interface Modules________________Window Size

As frames are accepted into a port on the FRM, they are wrapped in internal protocol blocks andsent across the network. The window size, as configured by the DLCI THROUGHPUT TUNINGparameter, determines the number of blocks (1, 3, 5, 7, or open) that can be sent before it mustwait for an acknowledgment from the receiving end before sending additional frames. Thedefault is 7; options 1 to 7 use GOS4; the open option uses GOS3.

Throughput tuning allows the trade-off between throughput and delay to be adjusted. Highervalues, such as open, usually improve throughput; lower values, such as 1, usually reduce delayfor other network traffic. Window size is especially important when using internodal trunks.

Congestion Management

The availability of up to 507 DLCIs per FRM permits considerable flexibility in networkengineering. If extended measurements are administered, each module supports a maximum of300 DLCIs. If traffic occasionally exceeds engineered specifications, the use of a large number ofDLCIs can produce congestion problems. In that case, the network uses congestion managementto recover. To avoid problems, each DLCI can be managed separately via the CIR, Bc, and Be.

CIR

The CIR is administered separately for each DLCI. A PVC is identified by two DLCIs (one ateach endpoint). Different CIR options can be administered for each direction of data flow in aPVC. When the CIR option is administered for the DLCI, the CIR is specified as a data rate. Theminimum value for an individual DLCI is 2400 bps and the maximum value is equal to the portline speed. Because of the assumption that all DLCIs cannot be active simultaneously, theaggregate total for all DLCIs on one port can exceed the port line speed.

The administrator can set a threshold for each port, and if the sum of egress CIRs for all DLCIson the port exceeds this threshold, a warning is issued. The threshold value can be up to 10 timesthe port line speed.

Bc Size

The size of the Bc is specified in bits. The maximum Bc that can be selected is a function of theCIR that is administered and a time interval, T, during which the burst (Bc) at the administeredCIR might last. The maximum interval, T, that is allowed is 15 seconds. The minimum numberof bits that can be administered for Bc is 256:

Bc = T × CIR; maximum Bc = 15 seconds × CIR

For example, if CIR is 64 Kbps, the prompt for Bc would show the values ranging from 256 to960000 bits.

Recommendation. When selecting the value of Bc, set the value of Bc greater than or equalto the longest expected burst. This should be large enough to cover the largest frame that the portreceives. Bear in mind the time interval corresponding to the Bc.


Interface Modules________________Be Size

The size of the Be can be specified in bits or it can be entered as a percentage of the maximumport line speed. If a percentage is entered, the maximum possible value of the Be, Be(max) iscalculated so the sum of Bc and Be(max) equals the port line speed. The specified percentage isthen applied to Be(max) to obtain Be(percent). The following equation illustrates howBe(percent) is derived from Be(max) :

Be(max) = ( LS × T ) − BcBe(percent) = Be(max) × P

Where: P is the specified percentage, expressed as a decimal fraction.LS is the port line speed (in bps).T is the time interval (in seconds); where: T equals CIR divided by Bc.

Consider the following example:

Port line speed: LS = 1.536 Mbps

Committed Information Rate: CIR = 64 Kbps

Committed Burst: Bc = 64 Kbits

Time interval: T = 1 second

90% is entered for Be.

In this case, Be is evaluated as follows:

— Be(max) = LS × T − Bc = (1536 Kbps × 1 sec) − 64 Kbps = 1472 Kbps

— Be = 1472 Kbps × 0.90 = 1324.8 Kbps

This allows the administrator to set up a high limit for the Be so any DLCI can run in burstsup to the line speed of the port without dropping frames. If the Be is set below the line speed,however, a sustained burst through the DLCI could result in the FRM discarding frames. IfBe is specified in bits, the maximum possible value of Be is 15 seconds times CIR for thelocal end and 30,720,000 bits for the remote end.

Bc, Be, and Discard Rate

The FRM implements the algorithm specified in the ANSI T1.606a-1992 standard that is used tocontrol the rate in which data is released into the network on a DLCI level. Based on a set ofparameters, traffic is either discarded or is released into the network marked as "committed data"or "excess data".

The FRM sends data into the network that is reserved at a rate less than or equal to the CIR. Datait receives above the CIR, but below the Be rate, is still sent into the network; but the FRM marksthe frames with the discard eligibility (DE) bit set. This DE bit indicates whether the frame canbe discarded during congestion. Frames with the DE bit set are discarded before frames withoutthe DE bit set. Data received above Be rate is discarded. The configured Bc and/or Be should belarge enough to accommodate the maximum frame size.


Interface Modules________________For a steady load situation, the following figure illustrates

the rate at which frames are sent through the network without DE set

the rate at which frames are sent through the network with DE set

the rate at which frames are discarded

Bits

Time

Frames Sentinto theNetwork withoutDE Set

Load 1

Frames Sentinto theNetwork withDE Set

Load 2

Load 3

FramesDiscarded atthe FRMInterface

Access Rate

Burst inExcessof CIR= Be+Bc

T

CIR= BcT

FIGURE 5-2. CIR, Be Rate, and Discard Rate


Interface Modules________________Referring to the previous figure, consider Load 1, Load 2, and Load 3. With an offered load ofLoad 1, which is under the CIR, the FRM sends all frames through the network without DE set.With the higher load of Load 2, which exceeds the CIR but is within the excess configured, someframes are sent into the network without DE set, but some frames are sent with DE set. Thehighest load depicted is Load 3. It exceeds both the CIR and Be rates, has some frames passedinto the network without DE set, has some sent with DE set, and some discarded at the FRMinterface. A few formulas show a simplified case with these assumptions:

The load or rate of frame arrival is constant.

The load is greater than (Bc + Be)T; where: T = Bc/CIR.

The formulas show the percentage of the load presented to the FRM that is considered Bc data,Be data, and the percentage that is discarded over time.

These examples are not intended to predict what any network might experience. They areincluded as an aid to understanding. The resulting percentages are approximations:

2A = % of data sent into the network without DE set =load bps

Bc bits/T seconds_ ______________ ×100 1

2B = % of data sent into the network without DE set =load bps

Be bits/T seconds_ ______________ ×100 1

2C = % of data discarded =1 −

load in bps(Bc + Be)/T_ __________

* 100

Where:

Bc is the committed burst from local device or committed burst from remote device.Be is the excess burst from local device or excess burst from remote device.CIR is the committed information rate from local device or remote device.T is derived from Bc over CIR.Load is the amount of user data transported in bits per second.

For example: If the load is 64,000 bits per second, CIR is 16,000 bits per second, Bc is 40,000bits, and Be is 60,000 bits, T is 2.5 seconds and 25% of the data is sent into the network withoutDE being set, 37.5% is sent into the network with DE set, and 37.5% is discarded:

2A = % of data sent into the network without DE set =64,000 bps

40,000 bits/2.5 seconds_ ___________________ ×100 = 25% 1

2B = % of data sent into the network without DE set =64,000 bps

60,000 bits/2.5 seconds_ ___________________ ×100 = 37.5% 1

2C = % of data discarded =1 −

64,000 bps(40,000 bits + 60,000 bits) / 2.5 seconds_ __________________________________

* 100 = 37.5%


Interface Modules________________Backbone Trunk Modules

Frame relay introduces certain high performance requirements for networking—in particular, theability to handle the large frame sizes allowed, which results in specific requirements for trunkmodules: some trunk modules are specifically recommended to carry frame relay traffic; othersare definitely not allowed.

Recommendations.

The recommended trunk for speeds from 56 Kbps to T1/E1 is the SWT or the Trunk-PQ.

The Trunk-T1 supports a similar range of line speeds, but has less internal buffer space thanthe SWT (its window size is 1); therefore, it allows less parameter tuning flexibility.

The recommended trunks for T3/E3 speeds are the Trunk-T3A, Trunk-E3A, Trunk-T3S, andTrunk-E3S, which are all supported in BNS-2000 networks.

Frame relay traffic should not be routed through Datakit VCS Generic 3.4 or earlier nodes.These nodes do not support the window size negotiation required for frame relay service.

Performance Issues

The performance obtained by a frame relay application is influenced by the networkconfiguration, particularly access line speeds, backbone trunk speeds, and the overall traffic load.Throughput and delay vary with the configuration; the slowest link in each end-to-end path is thecritical component for engineering of that path.

Many LAN applications provide error control and flow control capabilities. A frame relaynetwork discards frames as it becomes overloaded, causing the application to invoke errorrecovery procedures to reduce the perceived user throughput. To maximize this throughput,engineer the network with sufficient capacity to allow transfer of all data without saturation.

Engineering for Throughput

To provide good service, determine the estimated busy-hour load for each end-to-end connection.(The resulting traffic matrix describes the load from each source to each destination.) Add thehigher level protocol overhead and the frame relay LAPF overhead to get the offered load.

Calculate the load for each direction of transmission between endpoints and the network designedto support the maximum traffic for each path. Provision the links to allow for bursts of traffic20% to 30% above the average busy-hour offered load.

Determining Network Load

Precise traffic information is not always available. If exact information for the load at theinterface to the FRM is not available, estimate the expected load.

Each LAN has different characteristics for typical load before saturation, supported protocols andapplications, overhead, and typical frame sizes. Make assumptions to approximate offered load.


Interface Modules________________The following example shows some typical values for a Transmission Control Protocol/InternetProtocol (TCP/IP) Ethernet network.

Assume a utilization of 20%; since the LAN operates at 10 Mbps, this equals 2 Mbps. Follow theguideline that approximately 20% of the traffic on a LAN goes into the WAN and increases thevalue by 30% to account for bursts. The result is a value of 520 Kbps per LAN. For aconservative estimate and to provide higher bandwidth for the access link, assume this level oftraffic is in one direction.

For an average frame size of 576 bytes, the offered load to the router is determined by theefficiency of the Ethernet:

Offered Load frame size_ __ _ _ _____________________________ × data rateto router (frame size + Ethernet overhead)

576 bytes_ __ _ _ ______________________ × 520 Kbps(576 bytes + 18 bytes)

_ __ _ 504 Kbps

For this example, 504 Kbps is the load provided to the router after the Ethernet overhead isstripped off.

Now include the effect of the LAPF overhead, which increases the load offered by the router tothe FRM:

Offered Load (frame size + router encapsulation + LAPF overhead)_ __ _ _ _____________________________________________ × data rateto FRM frame size

(576 bytes + 2 bytes + 6 bytes)_ __ _ _ _____________________________ × 504 Kbps576 bytes

_ __ _ 511 Kbps

This means that the access link must be at least a fractional T1 link operating at 576 Kbps.

Use the average frame size of 576 bytes to determine the aggregate throughput of the FRM. Themaximum aggregate throughput for an FRM (V.35) is 3700 Kbps. Assuming that the throughputis evenly distributed for input and output, the throughput in one direction is 1850 Kbps. Dividethis throughput by the offered load per router to determine the number of ports that can be usedper FRM. For this example, three routers could be connected to a single FRM.

After the network is in service, refine the numbers by collecting statistics from the routers.


Interface Modules________________User Perception of Network Efficiency

This section examines user perception of network performance related to throughput. Theaggregate throughput reflects throughput in terms of the LAPF information field. By analyzing asingle T1 access line running at 1.536 Mbps, calculate the theoretical maximum throughput perdirection of transmission. Assuming a 1500-byte information field, the efficiency can becalculated as shown in the following equation:

information field sizeEfficiency

_ __ _ _ _________________________________(information field size + LAPF overhead)

1500 bytes_ __ _ _ ____________________(1500 bytes + 6 bytes)

_ __ _ 99.6 %

The result is in a maximum single throughput rate of 1.529 Mbps and an aggregate bi-directionalthroughput rate of 3.059 Mbps. Because this is less than the aggregate throughput of an FRM, asingle port can sustain it.

The maximum theoretical throughput does not reflect the perception of throughput, which takesinto account the effect of overhead associated with higher level protocols. From a userperspective, throughput is measured as the "real user data" transferred per unit time from point Ato point B. An application passes blocks of data to lower levels in the protocol stack. At eachlevel, the possibility of additional overhead affects the user perception of throughput.

The following example of a file transfer using a file transfer protocol (FTP) application shows theinfluence of additional higher level protocol overhead. The user may measure the time from entryof the get command to the completion of the file transfer. Additional time for applicationhandshaking, acknowledgments, end-to-end propagation delay including access/egress times, andprocessing delay further reduce the throughput.

Assume a 10,000-byte file is being transferred between two Ethernet LANs via a frame relaynetwork. Both the application and the router support a maximum transmission unit (MTU) sizeof 1500 bytes. The TCP level adds 20 bytes of overhead to each Ethernet packet and the InternetProtocol (IP) level adds an additional 20 bytes. Therefore, each packet can contain a maximum of1460 bytes of "real user data."

To transfer the 10,000-byte file, it is necessary to send seven packets—six full packets with 1460bytes of user data and a seventh packet with the remaining 1240 bytes. Each packet wouldcontain 40 bytes of higher level protocol overhead—20 from TCP and 20 from IP. These packetsare sent over the network in seven frame relay frames. Each packet is encapsulated using RequestFor Comment (RFC) 1294, a method of multi-protocol encapsulation over frame relay that addstwo bytes per frame. The LAPF overhead adds an additional six bytes of overhead. Therefore,each frame contains 48 bytes of overhead when all levels of the protocol stack are considered.


Interface Modules________________The total overhead to transfer the 10,000-byte file in seven frames is 336 bytes. From the userperspective the efficiency of this file transfer is shown in the following equation:

size of file transferEfficiency

_ __ _ _ ______________________________(size of file transfer + total overhead)

10000 bytes_ __ _ _ _________________________(10000 bytes + 336 bytes)

_ __ _ 96.7 %

The result is a perceived throughput of 1.486 Mbps. Processing delays, handshaking,acknowledgments, and other factors further reduce this throughput.

Each additional millisecond of delay adds the equivalent of 192 bytes of overhead fortransmissions at 1.536 Mbps. It is important, therefore, not to confuse module throughput basedon LAPF information fields with user throughput based on "real user data" transfer.

Backbone Trunk Speeds

After aggregating the total expected traffic into the network, begin specifying the projected loadon the backbone trunks. Examine the expected load during peak traffic periods and allow forbursts of traffic that exceed that level. This allowance is important in preventing the buildup ofqueues in the network.

When planning for trunk loading, consider the overhead factors—LAN overheads, routingprotocols, frame relay headers—associated with the access/egress data streams, and account fornetwork overhead when the traffic is routed across internodal facilities.

For an SWT, consider a 16% overhead on frame relay traffic when calculating trunk loads.Calculate, for example, a 64 Kbps access link as using 74 Kbps of an SWT running at T1 speed,if all traffic from the port is to traverse the same trunk. Understanding the nature of theapplications supported through the frame relay network also allows average utilization levelestimations, which can be revised as a traffic profile is built up via various performance reports,such as dmeas, dstat, and StarKeeper II NMS reports. These utilization factors enable theconcentration ratio on trunks to be determined as the network is engineered.

Engineering for Delay

In remote login applications, the network delay affects echoplex performance as seen by users.This section shows an example of computing delays into and out of the network for a typicalTCP/IP TELNET session. During these sessions, each character is transmitted across the networkto the remote host. The remote host echoes by transmitting the character back to the local consolefor display on the monitor. The actual sequence results in a 64-byte Ethernet frame transmittedacross the LAN. After the maintenance administration center (MAC) header and trailer arestripped, a 46-byte IP packet remains, which becomes the information field for frame relaytransmission.


Interface Modules________________For example, assume a user connected to an Ethernet LAN establishes a TELNET session acrossa frame relay network to a remote host. An IP router connects the LAN to a frame relay networkat 56 Kbps; the remote host is connected to the network using the same configuration. Thefollowing calculation shows the ingress and egress delays based on the 56 Kbps access links:

(TELNET packet size + router encapsulation + LAPF overhead)Ingress/Egress Delay

_ __ _ _ _________________________________________________line speed

(46 bytes + 2 bytes + 6 bytes) × 8 bits/byte_ __ _ _ _________________________________56000 bits/sec

_ __ _ 7.7 msec

The following individual delays should be added to both ingress and egress delays:

LAN delay

router delay

propagation delay (based on total facility length throughout the network, estimated as 8 msecfor each 1,000 miles)

FRM delay (typically fewer than 8 msec per module for frames less than 1600 octets inlength)

network delays depending on trunk speeds and traffic

host delay

The sum of all these delays is the estimated one-way delay. Double this figure, less host delay, tocalculate the round-trip delay. Acceptable performance for echoplex applications usually requiresround-trip delays of no more than 200 to 250 msec.

The nping port diagnostic of the diagnose frm command can be used to measure delay.

Engineering Checklist

The following steps are suggestions for planning a frame relay network based on the assumptionthat no network components have been configured. If network components are already in place,adjust the steps accordingly.

1. Estimate the amount of traffic from each LAN to enter and leave the WAN at each location.

2. Size the access and trunk line speeds required for these basic traffic levels.

3. Determine the values for CIR, Bc, Be.

4. Determine the impact of the committed rates on throughput and delay.


Interface Modules________________5. Adjust the line speeds and window sizes as needed to meet these new requirements.

6. Determine the impact of LAN traffic on the delay performance of non-LAN traffic.

7. Adjust the line speeds and committed rates to account for this interactive traffic.

8. Use the dmeas and dstat commands to monitor performance and determine how closely theactual traffic corresponds to the initial estimates.

9. Expect growth in traffic and adjust the network accordingly.


Interface Modules________________FRM-M2

This section provides information to assist network engineering personnel in planning andmanaging a network that includes FRM-M2s. It presents guidelines for selecting configurationparameters and options, examines network performance issues related to frame relay operations,and provides an engineering checklist.

Addressing

The node supports the data link connection identifier (DLCI) for permanent virtual circuits(PVCs) through the FRM-M2. Each PVC requires two DLCIs. When a DLCI is administered,the Control Computer associates it with a channel number in the FRM-M2. A PVC call is set upto associate one port and DLCI (where the PVC originates), with a second port and DLCI (thedestination of the PVC) in the network.

The frame relay address field uses two, three, or four octets to carry the DLCI. Some DLCIs arereserved for other functions. In operation, each module supports a maximum of 2000 DLCIs.Any DLCI numbers can be chosen from among those available; they do not have to formcontiguous sequences.

The format for an FRM-M2 address in a node is:

Mnemonic address: [network/area/exchange/]local.module.port.virtual port.DLCI

X.121 address: [DNIC/SR/SA/EPN].module.port.virtual port.DLCI

In these address formats, port is the physical port number, which is a number from 1 to 6 for aChT1/ChE1; and virtual port is a number from 1 to 24 for a ChT1 or 1 to 31 for a ChE1.

Interworking

The FRM-M2 interworks with FRM and LPM modules with the following restrictions:

if the FRM or LPM resides on a node that is running a release prior to BNS-2000 Release 4.0or any Datakit II VCS release, the call must originate from the FRM-M2 module

AAL5 is automatically used if the destination endpoint is an FRM-M2 on the same node, or ifthe destination endpoint is an FRM-M2 on another node, and the PVC goes over a TRK-T3Aor E3A using BNS-2000 Release 4.0, Build 65 and up

if session maintenance is used, ensure that only TRK-T3A or E3A trunks using BNS-2000Release 4.0 are in the reroute path, or data corruption may occur


Interface Modules________________Configurable Options

The following section explains the configurable options that affect FRM-M2 performance.

Module Throughput

The FRM-M2 (ChT1) supports six ports with up to 24 virtual ports on each physical port, whichcan be configured for a total aggregate speed of 1536 Kbps. The FRM-M2 (ChE1) supports up to31 virtual ports on each physical port, which can be configured for a total aggregate speed of 1984Kbps. The FRM-M2 can support 100% line utilization on all ports simultaneously in bothreceive and transmit directions for large frame sizes. Here, the module throughput is limited onlyby the port speeds. For small frame sizes, the FRM-M2 throughput is limited by a maximumframe rate. The maximum frame rate depends on frame size.

Tables 2-1 and 2-2 show the maximum frame rate for selected frame sizes for the FRM-M2 ChT1and ChE1 respectively. In these tables, the frame size is the size of the information field; it doesnot include the LAPF overhead. These tables show that the FRM-M2 maximum frame rate ishigher when circuits use AAL5. The FRM-M2 automatically selects AAL5 for virtual circuitsconnecting FRM-M2 modules located on the same node, and to FRM-M2 modules on remotenodes when the virtual circuits traverse TRK-T3A or E3A modules using BNS-2000 Release 4.0,Build 65 and up. The FRM-M2 selects URP for virtual circuits that connect to FRM-M1 or otherM1-shelf modules, or when the virtual circuits traverse other trunk module types.

TABLE 5-15. T1 Small Frame Performance

_ ____________________________________________________________Frame FrameSize Rate Line Utilization with n Ports_ _____________________________________________________________ ____________________________________________________________

1 2 3 4 5 6_ ____________________________________________________________URP Virtual Circuits_ ____________________________________________________________

1 24,800 39% 19% 13% 10% 8% 6%_ ____________________________________________________________32 21,000 100% 100% 67% 51% 40% 34%_ ____________________________________________________________64 18,700 100% 100% 100% 84% 67% 56%_ ____________________________________________________________

262 and up

8,694

100%

100%

100%

100%

100%

100%_ ____________________________________________________________AAL5 Virtual Circuits_ ____________________________________________________________

1 28,600 45% 22% 15% 11% 9% 7%_ ____________________________________________________________32 27,500 100% 100% 88% 66% 53% 44%_ ____________________________________________________________64 23,800 100% 100% 100% 100% 86% 71%_ ____________________________________________________________

128 and up 17,323 100% 100% 100% 100% 100% 100%_ ____________________________________________________________


Interface Modules________________TABLE 5-16. E1 Small Frame Performance

_ ____________________________________________________________Frame FrameSize Rate Line Utilization with n Ports_ _____________________________________________________________ ____________________________________________________________

1 2 3 4 5 6_ ____________________________________________________________URP Virtual Circuits_ ____________________________________________________________

1 25,900 31% 16% 10% 8% 6% 5%_ ____________________________________________________________32 22,000 100% 82% 55% 41% 33% 27%_ ____________________________________________________________64 18,900 100% 100% 88% 66% 53% 44%_ ____________________________________________________________

262 8,850 100% 100% 100% 100% 95% 79%_ ____________________________________________________________576 and up

5,140

100%

100%

100%

100%

100%

100%_ ____________________________________________________________AAL5 Virtual Circuits_ ____________________________________________________________

1 28,600 35% 17% 12% 9% 7% 6%_ ____________________________________________________________32 27,500 100% 100% 68% 51% 41% 34%_ ____________________________________________________________64 24,800 100% 100% 100% 86% 69% 58%_ ____________________________________________________________

128 and up 22,375 100% 100% 100% 100% 100% 100%_ ____________________________________________________________

Avoid configurations where the traffic load exceeds the module’s maximum frame rate. Theaverage frame size and frame rate for each virtual port can be determined by using the dmeasoperations command on the node console or the report command on StarKeeper II NMS Core.

Buffer Congestion Notification

The FRM-M2 maintains separate buffer pools for each virtual port. These pools are furtherdivided into receive and transmit pools. The buffer pools enter congestion when 85% of thebuffers are in use; they leave congestion when the utilization drops below 55%. The dmeasoperations command provides buffer congestion measurements for each virtual port.

When a virtual port’s receive buffer pool becomes congested, the FRM-M2 module sets theForward Explicit Congestion Notification (FECN) bit in frames moving along the receive pathand the Backward Explicit Congestion Notification (BECN) bit in frames moving along thetransmit path. Similarly, when a virtual port’s transmit buffer pool becomes congested, themodule sets the FECN bit in frames moving along the transmit path and the BECN bit in framesmoving along the receive path. Congestion counts are included in the output of the dmeascommand.


Interface Modules________________Number of PVCs

The FRM-M2 can support 2000 virtual circuits; each virtual circuit maps to a pair of DLCIs.Thus, a given frame relay endpoint can communicate with up to 2000 other endpoints. The totalnumber of frame relay endpoints in the network can, however, be much greater than 2000. Avirtual circuit is administered as a predefined destination (PDD); each PDD corresponds to onePVC.

Number of DLCIs

Each module supports a maximum of 2000 DLCIs. A node supports 20,000 DLCIs.

Maximum Length of Information Field

The frame relay standard enables the network administrator to set a limit for the maximumnumber of octets in the information field of each frame by configuring the MAXIMUM FRAMESIZE parameter. A separate limit may be specified for each virtual port, ranging in size from262 to 4096 octets. The default is 4096. If a frame is received that is larger than the maximumsize allowed, it is discarded and an alarm is sent to the node console.

Recommendation. To optimize the buffering over intermediate trunks, configure the smallestmaximum frame size that meets the needs of the application.

XON/XOFF Flow Control

The FRM-M2 can be configured to use the LMI for PVC management. This enables the FRM-M2 to respond to buffer congestion as follows:

When a virtual port’s receive buffer pool becomes congested, the module sends an XOFF tothe access device that is connected to the virtual port. The XOFF is indicated by clearing theR-bit in a PVC status message.

When a virtual port’s receive buffer pool is no longer congested, the module sends an XON.The XON is indicated by clearing the R-bit in a PVC status message.

When a virtual port’s transmit buffer pool becomes congested, the module causes each virtualport connected to the congested virtual port to issue an XOFF to the access device connectedto it. The XOFF is indicated by clearing the R-bit in a PVC status message.

When a virtual port’s transmit buffer pool is no longer congested, the module causes eachvirtual port connected to the previously congested virtual port to issue an XON to the accessdevice connected to it. The XON is indicated by clearing the R-bit in a PVC status message.

The FRM-M2 uses the same criteria to determine congestion for sending XONs and XOFFs as itdoes for setting Forward Explicit Congestion Notification (FECN) and Backward ExplicitCongestion Notification (BECN) bits.


Interface Modules________________Congestion Management

The availability of up to 2000 DLCIs per FRM-M2 permits considerable flexibility in networkengineering. If traffic occasionally exceeds engineered specifications, the use of a large numberof DLCIs can produce congestion problems. In that case, the network uses congestionmanagement to recover. To avoid problems, each DLCI can be managed separately via the CIR,Bc, and Be.

DLCI Data Rates The FRM-M2 supports three optional parameters to control the data rates forDLCIs:


committed Burst size (Bc)

excess Burst size (Be)


CIR The CIR is administered separately for each DLCI. A PVC is identified by two DLCIs(one at each endpoint). Different CIR options can be administered for each direction of data flowin a PVC. When the CIR option is administered for the DLCI, the CIR is specified as a data rate.The minimum value for an individual DLCI is 2400 bps and the maximum value is equal to thevirtual port line speed. Because of the assumption that all DLCIs cannot be activesimultaneously, the aggregate total for all DLCIs on one virtual port can exceed the virtual portline speed.

The administrator can set a threshold for each virtual port, and if the sum of egress CIRs for allDLCIs on the virtual port exceeds this threshold, a warning is issued. The threshold value can beup to 10 times the virtual port line speed.

Bc Size The size of the Bc is specified in bits. The maximum Bc that can be selected is afunction of the CIR that is administered. The minimum number of bits that can be administeredfor Bc is 256.

maximum Bc = 15 seconds × CIR

For example, if CIR is 64 Kbps, the prompt for Bc would show the values ranging from 256 to960000 bits.

Recommendation. When selecting the value of Bc, set the value of Bc greater than or equalto the longest expected burst. This should be large enough to cover the largest frame that thevirtual port receives. Bear in mind the time interval corresponding to the Bc.

Be Size The size of the Be can be specified in bits or it can be entered as a percentage of themaximum virtual port line speed. If a percentage is entered, the maximum possible value of theBe, Be(max) is calculated so the sum of Bc and Be(max) equals the virtual port line speed. Thespecified percentage is then applied to Be(max) to obtain Be(percent). The following equationillustrates how Be(percent) is derived from Be(max) :

Be(max) = ( LS × T ) − BcBe(percent) = Be(max) × P


Interface Modules________________Where: P is the specified percentage, expressed as a decimal fraction.

LS is the virtual port line speed (in bps).T is the time interval (in seconds); where: T equals CIR divided by Bc.

Consider the following example:

Virtual port line speed: LS = 1.536 Mbps

Committed Information Rate: CIR = 64 Kbps

Committed Burst: Bc = 64 Kbits

Time interval: T = 1 second

90% is entered for Be.

In this case, Be is evaluated as follows:

— Be(max) = LS × T − Bc = (1536 Kbps × 1 sec) − 64 Kbps = 1472 Kbps

— Be = 1472 Kbps × 0.90 = 1324.8 Kbps

This allows the administrator to set up a high limit for the Be so any DLCI can run in burstsup to the line speed of the virtual port without dropping frames. If the Be is set below the linespeed, however, a sustained burst through the DLCI could result in the FRM-M2 discardingframes. If Be is specified in bits, the maximum possible value of Be is 15 seconds times CIRfor the local end and 30,720,000 bits for the remote end.


Interface Modules________________Bc, Be, and Discard Rate The FRM-M2 implements the algorithm specified in the ANSIT1.606a-1992 standard that is used to control the rate in which data is released into the networkon a DLCI level. Based on a set of parameters, traffic is either discarded or is released into thenetwork marked as "committed data" or "excess data".

The FRM-M2 sends data into the network that is reserved at a rate less than or equal to the CIR.Data it receives above the CIR, but below the Be rate, is still sent into the network; but the FRM-M2 marks the frames with the discard eligibility (DE) bit set. This DE bit indicates whether theframe can be discarded during congestion. Frames with the DE bit set are discarded beforeframes without the DE bit set. Data received above the Be rate is discarded. The configured Bcand/or Be should be large enough to accommodate the maximum frame size. For a steady loadsituation, the following figure illustrates

the rate at which frames are sent through the network without DE set

the rate at which frames are sent through the network with DE set

the rate at which frames are discarded


Interface Modules________________

Bits

Time

Frames Sentinto theNetwork withoutDE Set

Load 1

Frames Sentinto theNetwork withDE Set

Load 2

Load 3

FramesDiscarded atthe FRM-M2Interface

Access Rate

Burst inExcessof CIR= Be+Bc

T

CIR= BcT

FIGURE 5-3. CIR, Be Rate, and Discard Rate

Referring to the previous figure, consider Load 1, Load 2, and Load 3. With an offered load ofLoad 1, which is under the CIR, the FRM-M2 sends all frames through the network without DEset. With the higher load of Load 2, which exceeds the CIR but is within the excess configured,some frames are sent into the network without DE set, but some frames are sent with DE set. Thehighest load depicted is Load 3. It exceeds both the CIR and Be rates, has some frames passedinto the network without DE set, has some sent with DE set, and some discarded at the FRM-M2interface. A few formulas show a simplified case with these assumptions:

The load or rate of frame arrival is constant.

The load is greater than (Bc + Be)T; where: T = Bc/CIR.

The formulas show the percentage of the load presented to the FRM-M2 that is considered Bcdata, Be data, and the percentage that is discarded over time.


Interface Modules________________These examples are not intended to predict what any network might experience. They areincluded as an aid to understanding. The resulting percentages are approximations:

A = % of data sent into the network without DE set =load bps

Bc bits/T seconds_ ______________ ×100

B = % of data sent into the network with DE set =load bps

Be bits/T seconds_ ______________ ×100

C = % of data discarded =1 −

load in bps(Bc + Be)/T_ __________

* 100

Where:

Bc is the committed burst from local device or committed burst from remote device.Be is the excess burst from local device or excess burst from remote device.CIR is the committed information rate from local device or remote device.T is derived from Bc/CIR.Load is the amount of user data transported in bits per second.

For example: If the load is 64,000 bits per second, CIR is 16,000 bits per second, Bc is 40,000bits, and Be is 60,000 bits, T is 2.5 seconds and 25% of the data is sent into the network withoutDE being set, 37.5% is sent into the network with DE set, and 37.5% is discarded:

A = % of data sent into the network without DE set =64,000 bps

40,000 bits/2.5 seconds_ ___________________ ×100 = 25%

B = % of data sent into the network with DE set =64,000 bps

60,000 bits/2.5 seconds_ ___________________ ×100 = 37.5%

C = % of data discarded =1 −

64,000 bps(40,000 bits + 60,000 bits) / 2.5 seconds_ __________________________________

* 100 = 37.5%


Interface Modules________________Backbone Trunk Modules

Frame relay introduces certain high performance requirements for networking—in particular, theability to handle the large frame sizes allowed, which results in specific requirements for trunkmodules: some trunk modules are specifically recommended to carry frame relay traffic; othersare definitely not allowed.

Recommendations.

The recommended trunks for T3/E3 speeds are the Trunk-T3A, Trunk-E3A, Trunk-T3S, andTrunk-E3S, which are all supported in BNS-2000 networks.


Frame relay traffic should not be routed through Datakit VCS Generic 3.4 or earlier nodes.

If AAL5 is used and the destination endpoint is internodal, the PVC must go over a TRK-T3Aor E3A using BNS-2000 Release 4.0 or later.


Interface Modules________________Performance Issues

The performance obtained by a frame relay application is influenced by the networkconfiguration, particularly access line speeds, backbone trunk speeds, and the overall traffic load.Throughput and delay vary with the configuration; the slowest link in each end-to-end path is thecritical component for engineering of that path.

Many LAN applications provide error control and flow control capabilities. A frame relaynetwork discards frames as it becomes overloaded, causing the application to invoke errorrecovery procedures to reduce the perceived user throughput. To maximize this throughput,engineer the network with sufficient capacity to allow transfer of all data without saturation.

Engineering for Throughput

To provide good service, determine the estimated busy-hour load for each end-to-end connection.(The resulting traffic matrix describes the load from each source to each destination.) Add thehigher level protocol overhead and the frame relay LAPF overhead to get the offered load.

Calculate the load for each direction of transmission between endpoints and the network designedto support the maximum traffic for each path. Provision the links to allow for bursts of traffic20% to 30% above the average busy-hour offered load.

Determining Network Load

Precise traffic information is not always available. If exact information for the load at theinterface to the FRM-M2 is not available, estimate the expected load.

Each LAN has different characteristics for typical load before saturation, supported protocols andapplications, overhead, and typical frame sizes. Make assumptions to approximate offered load.

The following example shows some typical values for a Transmission Control Protocol/InternetProtocol (TCP/IP) Ethernet network.

Assume a utilization of 20%; since the LAN operates at 10 Mbps, this equals 2 Mbps. Follow theguideline that approximately 20% of the traffic on a LAN goes into the WAN and increases thevalue by 30% to account for bursts. The result is a value of 520 Kbps per LAN. For aconservative estimate and to provide higher bandwidth for the access link, assume this level oftraffic is in one direction.


Interface Modules________________For an average frame size of 576 bytes, the offered load to the router is determined by theefficiency of the Ethernet:

Offered Load frame size_ __ _ _ _____________________________ × data rateto router (frame size + Ethernet overhead)

576 bytes_ __ _ _ ______________________ × 520 Kbps(576 bytes + 18 bytes)

_ __ _ 504 Kbps

For this example, 504 Kbps is the load provided to the router after the Ethernet overhead isstripped off.

Now include the effect of the LAPF overhead, which increases the load offered by the router tothe FRM-M2:

Offered Load (frame size + router encapsulation + LAPF overhead)_ __ _ _ _____________________________________________ × data rateto FRM-M2 frame size

(576 bytes + 2 bytes + 6 bytes)_ __ _ _ _____________________________ × 504 Kbps576 bytes

_ __ _ 511 Kbps or 887 Frames per Second

This means that the access link must be at least a fractional T1 link operating at 576 Kbps.

In this example, the average frame size is much greater than those for which the FRM-M2throughput is limited, so there is no concern about exceeding the module capacity.

After the network is in service, refine the numbers by using statistics collected from the routersand the output of the dmeas operations command (node console) or the report command(StarKeeper II NMS Core).


Interface Modules________________User Perception of Network Efficiency

This section examines user perception of network performance related to throughput. Theaggregate throughput reflects throughput in terms of the LAPF information field. By analyzing asingle T1 access line running at 1.536 Mbps, calculate the theoretical maximum throughput perdirection of transmission. Assuming a 1500-byte information field, the efficiency can becalculated as shown in the following equation:

information field sizeEfficiency

_ __ _ _ _________________________________(information field size + LAPF overhead)

1500 bytes_ __ _ _ ____________________(1500 bytes + 6 bytes)

_ __ _ 99.6 %

The result is in a maximum single throughput rate of 1.529 Mbps and an aggregate bi-directionalthroughput rate of 3.059 Mbps. Because this is less than the aggregate throughput of an FRM-M2, a single port can sustain it.

The maximum theoretical throughput does not reflect the perception of throughput, which takesinto account the effect of overhead associated with higher level protocols. From a userperspective, throughput is measured as the "real user data" transferred per unit time from point Ato point B. An application passes blocks of data to lower levels in the protocol stack. At eachlevel, the possibility of additional overhead affects the user perception of throughput.

The following example of a file transfer using a file transfer protocol (FTP) application shows theinfluence of additional higher level protocol overhead. The user may measure the time from entryof the get command to the completion of the file transfer. Additional time for applicationhandshaking, acknowledgments, end-to-end propagation delay including access/egress times, andprocessing delay further reduce the throughput.

Assume a 10,000-byte file is being transferred between two Ethernet LANs via a frame relaynetwork. Both the application and the router support a maximum transmission unit (MTU) sizeof 1500 bytes. The TCP level adds 20 bytes of overhead to each Ethernet packet and the InternetProtocol (IP) level adds an additional 20 bytes. Therefore, each packet can contain a maximum of1460 bytes of "real user data."

To transfer the 10,000-byte file, it is necessary to send seven packets—six full packets with 1460bytes of user data and a seventh packet with the remaining 1240 bytes. Each packet wouldcontain 40 bytes of higher level protocol overhead—20 from TCP and 20 from IP. These packetsare sent over the network in seven frame relay frames. Each packet is encapsulated using RequestFor Comment (RFC) 1294, a method of multi-protocol encapsulation over frame relay that addstwo bytes per frame. The LAPF overhead adds an additional six bytes of overhead. Therefore,each frame contains 48 bytes of overhead when all levels of the protocol stack are considered.


Interface Modules________________The total overhead to transfer the 10,000-byte file in seven frames is 336 bytes. From the userperspective the efficiency of this file transfer is shown in the following equation:

size of file transferEfficiency

_ __ _ _ ______________________________(size of file transfer + total overhead)

10000 bytes_ __ _ _ _________________________(10000 bytes + 336 bytes)

_ __ _ 96.7 %

The result is a perceived throughput of 1.486 Mbps. Processing delays, handshaking,acknowledgments, and other factors further reduce this throughput.

Each additional millisecond of delay adds the equivalent of 192 bytes of overhead fortransmissions at 1.536 Mbps. It is important, therefore, not to confuse module throughput basedon LAPF information fields with user throughput based on "real user data" transfer.


After aggregating the total expected traffic into the network, begin specifying the projected loadon the backbone trunks. Examine the expected load during peak traffic periods and allow forbursts of traffic that exceed that level. This allowance is important in preventing the buildup ofqueues in the network.

When planning for trunk loading, consider the overhead factors—LAN overheads, routingprotocols, frame relay headers—associated with the access/egress data streams, and account fornetwork overhead when the traffic is routed across internodal facilities.

For an SWT, consider a 16% overhead on frame relay traffic when calculating trunk loads.Calculate, for example, a 64 Kbps access link as using 74 Kbps of an SWT running at T1 speed,if all traffic from the port is to traverse the same trunk. Understanding the nature of theapplications supported through the frame relay network also allows average utilization levelestimations, which can be revised as a traffic profile is built up via various performance reports,such as dmeas, dstat, and StarKeeper II NMS reports. These utilization factors enable theconcentration ratio on trunks to be determined as the network is engineered.


Interface Modules________________Engineering for Delay

In remote login applications, the network delay affects echoplex performance as seen by users.This section shows an example of computing delays into and out of the network for a typicalTCP/IP TELNET session. During these sessions, each character is transmitted across the networkto the remote host. The remote host echoes by transmitting the character back to the local consolefor display on the monitor. The actual sequence results in a 64-byte Ethernet frame transmittedacross the LAN. After the media access control (MAC) header and trailer are stripped, a 46-byteIP packet remains, which becomes the information field for frame relay transmission.

For example, assume a user connected to an Ethernet LAN establishes a TELNET session acrossa frame relay network to a remote host. An IP router connects the LAN to a frame relay networkat 56 Kbps; the remote host is connected to the network using the same configuration. Thefollowing calculation shows the ingress and egress delays based on the 56 Kbps access links:

(TELNET packet size + router encapsulation + LAPF overhead)Ingress/Egress Delay

_ __ _ _ _________________________________________________line speed

(46 bytes + 2 bytes + 6 bytes) × 8 bits/byte_ __ _ _ _________________________________56000 bits/sec

_ __ _ 7.7 msec

The following individual delays should be added to both ingress and egress delays:

LAN delay

router delay

propagation delay (based on total facility length throughout the network, estimated as 8 msecfor each 1,000 miles)

FRM-M2 delay (typically fewer than 8 msec per module for frames less than 1600 octets inlength)

network delays depending on trunk speeds and traffic

host delay

The sum of all these delays is the estimated one-way delay. Double this figure, less host delay, tocalculate the round-trip delay. Acceptable performance for echoplex applications usually requiresround-trip delays of no more than 200 to 250 msec.

The nping test, which is a test type found in the diagnose frm-m2 command, can be used tomeasure delay.


Interface Modules________________Engineering Checklist

The following steps are suggestions for planning a frame relay network based on the assumptionthat no network components have been configured. If network components are already in place,adjust the steps accordingly.

1. Estimate the amount of traffic from each LAN to enter and leave the WAN at each location.

2. Size the access and trunk line speeds required for these basic traffic levels.

3. Determine the values for CIR, Bc, Be.

4. Determine the impact of the committed rates on throughput and delay.

5. Adjust the line speeds and window sizes as needed to meet these new requirements.

6. Determine the impact of LAN traffic on the delay performance of non-LAN traffic.

7. Adjust the line speeds and committed rates to account for this interactive traffic.

8. Use the dmeas and dstat commands to monitor performance and determine how closely theactual traffic corresponds to the initial estimates.

9. Expect growth in traffic and adjust the network accordingly.

GAR

The Group Address Resolver (GAR) module provides the capabilities of a Group Address Agent(GAA). It is used only in SMDS networks serving as a GAA for group addresses. Up to eightGARs per agent network are allowed.

The GAR module can only be installed in Series M2 Shelves that are numbered 0, 1, 2, or 3. Itcannot be installed in Series M2 Extenstion Shelves numbered 6 or 7.

Because the function of the GAR module is to duplicate data, it has the potential of congestingthe network. Up to 128 group members can be assigned per group address; and depending on thesize and number of L2 PDUs in a message, network congestion can occur.

To protect network resources, a maximum arrival rate (MAR) can be specified for each groupaddress. A MAR is specified in thousands of post-resolved L2 PDUs per second, which is thenumber of L2 PDUs in the incoming message in KPDUs per second multiplied by the number ofmembers in the group address. The default is 60 K post-resolved PDUs per second and themaximum is 150 K. For each message, the GAR determines, on a source address basis, whetherit can meet the budget allocated by the MAR; if it cannot meet the budget, the message isdiscarded.

Network and GAR congestion can be monitored using SMEAS reports. In addition, the MARsfor the group addresses and the number of GARs should be engineered accordingly.


Interface Modules________________LPM

The LAN Protocol Module (LPM) provides the interface to support LAN interconnection to awide area network (WAN). To reach desired levels of service performance, several configurationoptions must be balanced. This section explains how configurable options affect LPM operations.

Physical Ethernet LAN Ports

The LPM supports up to two physical 10BASE-T LAN ports. Each port must be configured witha unique IP address and associated subnet mask. No two ports on an LPM, whether physical orvirtual, may be on the same IP subnetwork.

Virtual Frame Relay Ports

There may be up to 27 virtual frame relay ports on the LPM. As with physical LAN ports, eachvirtual frame relay port must be configured with a unique IP address and associated subnet maskfor the module. To establish PVCs from an LPM to other LPMs or FRMs, DLCIs must beconfigured. Each PVC on an LPM is associated with a virtual frame relay port. In general, it iseasiest to have a single virtual frame relay port on an LPM with all necessary PVCs groupedunder that single virtual port. However, there are reasons for grouping PVCs under severaldifferent virtual frame relay ports. One reason for partitioning the frame relay PVCs is forsecurity. For example, if it is desirable to have two IP subnetworks where the IP traffic from onesubnetwork is prevented from being routed to the other subnetwork, an LPM could be configuredto have two virtual frame relay ports and the port screening feature would be used to preventinternetwork traffic.

DLCIs, PVCs, and Channels

The LPM can support 507 frame relay PVCs. Each PVC maps to a pair of DLCIs, one for theoriginating endpoint of a PVC and one for the receiving endpoint of a PVC. Thus, a given LPMendpoint can communicate with up to 507 other endpoints. Since each PVC endpoint on anLPM is associated with a DLCI, the module supports a maximum of 507 DLCIs. When a DLCIis administered, the Control Computer associates it with a channel number in the LPM. So, forany LPM, the maximum number of channels, DLCIs, or PVC endpoints is 507. The totalnumber of PVC endpoints in the network can, however, be much greater than 507.


Interface Modules________________DLCI Data Rates

The LPM supports three optional parameters to control the data rates for DLCIs:


committed burst size (Bc)

excess burst size (Be)


In related options, the LPM supports throughput tuning for end-to-end flow control on eachDLCI. For information about these options, see the Window Size section in this chapter.

PVC Addressing

A PVC is administered by configuring an originating endpoint (DLCI) and a receiving endpoint(DLCI). Originating and receiving refers to which endpoint originates the call to establish thePVC and which end receives the call. In order to make the call, the originating DLCI isconfigured with a predefined destination (PDD). The PDD must have one of the followingformats:

Mnemonic address: [network/area/exchange/]local.[concentrator/]module.port.DLCI

X.121 address: [DNIC/SR/SA/EPN].[concentrator/]module.port.DLCI

In these address formats, port can be either the virtual frame relay port number on an LPM, or thephysical or virtual port number on an FRM or FRM-M2.


Interface Modules________________Maximum Transmission Unit

The maximum transmission unit (MTU) must be configured for each physical LAN and eachvirtual frame relay port on an LPM. The MTU enables the network administrator to set a limitfor the maximum number of octets in the information field that can be transmitted by a port. Forphysical LAN ports, the MTU SIZE can be configured to any value within the range of 576 to1492; the default is 1492. For virtual frame relay ports, the MTU SIZE can be configured to anyvalue within the range of 576 to 4096; the default is 1492.

Recommendation. The MTU SIZE for LAN ports should be set to the default of 1492 unlessdevices are on the LAN that are unable to receive IP frames of that size. If there are such devices,the MTU SIZE is set to the maximum frame size that such devices are capable of receiving.

In general, the MTU SIZE for virtual frame relay ports should also be set to the default, 1492.For data being routed from a LAN port to a virtual frame relay port, the maximum frame sizefrom the LAN would never be greater than 1492, so setting the MTU SIZE for a virtual framerelay port to a value larger than 1492 would not make a difference. A larger MTU SIZE is ofvalue only if data is routed directly from one virtual frame relay port to another one.

A lower MTU SIZE value than 1492 may be desirable in cases where the PVCs assigned to avirtual frame relay port are going through a trunk with small buffers. Refer to the BackboneTrunk Module Section for additional information.

Window Size

As frames are accepted into a port on the LPM, they are wrapped in internal protocol blocks andsent across the network. The window size, as configured by the DLCI THROUGHPUT TUNINGparameter, determines the number of blocks (1 to 7) that can be sent before waiting foracknowledgment from the receiving end. The default is 7.

Throughput tuning enables the trade-off between throughput and delay to be balanced. Highervalues usually improve throughput; lower values usually reduce delay for other network traffic.Window size is especially important when internodal trunks are used.

Congestion Management

The availability of up to 507 DLCIs per LPM permits considerable flexibility in networkengineering. If traffic occasionally exceeds engineered specifications, the use of a large numberof DLCIs can produce congestion problems. In that case, the network uses congestionmanagement to recover. To avoid problems, each DLCI can be managed separately via the CIR,Bc, and Be.

CIR

The CIR is administered separately for each DLCI. A PVC is identified by two DLCIs (one ateach endpoint). Different CIR options can be set for each direction of data flow in a PVC.


Interface Modules________________Maximum Aggregate CIR from Remote Devices

The MAXIMUM AGGREGATE CIR FROM REMOTE DEVICES parameter specifies a threshold forthe sum of the CIRs for all calls being established. If a value other than 0 is specified and thespecified threshold value is exceeded, this would cause PVC calls to be rejected. If a MAXIMUMAGGREGATE CIR is not being used, the value 0 should be selected; any call attempt in which theremote end of the PVC requires a CIR, even a zero CIR, is rejected.

The MAXIMUM AGGREGATE CIR may be up to four times the capacity of the virtual frame relayports of the LPM. Since these virtual ports are limited by the node backplane, the maximumaggregate CIR is limited to 32,768,000 bps.

Bc Size

The size of the Bc is specified in bits based on the CIR. The system calculates a range of valuesfor time intervals ranging from 0.5 seconds to 4 seconds. The default time interval is 1 second.The following illustrates how Bc is derived:

Bc = T × CIR

Where: T = [ 0.5, 1.0, 1.5, 2.0, 2.5, 3.0, 3.5, 4.0 ]

For example, if CIR is 64 Kbps, the prompt for Bc would offer the following values:

32, 64, 96, 128, 160, 192, 224, or 256 Kbps, with 64 Kbps as the default.

Recommendation. When selecting the value of Bc, set the value of Bc greater than or equalto the longest expected burst. Bear in mind the time interval corresponding to the Bc.

Be Size

The size of the Be may be specified in bits or percent and the maximum value can be up to theline speed.


Interface Modules________________Discard Eligibility Bits

The discard eligibility (DE) bit in each frame indicates whether the frame can be discarded duringnetwork congestion. The LPM sets the DE bits for frames presented at the interface, based on theconfigured values of CIR and Bc.

Since the total number of bits transmitted to the LPM during the time interval T is less than Bc,DE is set to 0 for all frames. Note that setting the DE bit to 0 does not prevent a frame frombeing discarded during congestion; it only indicates relative priority.

If the volume of data in an interval exceeds Bc, DE is set to 1 for all frames in excess of the Bc.

If the volume of data in an interval exceeds Be, the LPM discards all frames that exceedBe. Unlike the DE bit setting, Be actually prevents a DLCI from exceeding its configuredmaximum limit.

Discarded Frames

If the volume of data in an interval exceeds Be, the LPM discards all frames that exceed Be.Unlike the DE bit setting, Be actually prevents a DLCI from exceeding its administeredmaximum limit.

Congestion Management Over Time

For more information about congestion management and applying congestion management overtime, see the FRM section.

Port Screening Filters

The LPM allows screening lists of LAN physical ports (lanport) and/or virtual frame relay ports(frport) to be set up as an IP routing security measure. For an LPM port, whether a physical LANport or a virtual frame relay port, its screening list defines those other ports from which IP trafficcannot be routed. IP traffic originating from the excluded ports is discarded. Screening listsshould be symmetrical to prevent useless one-way transmission of data. For example, if frport 2screens out data from frport 3, then frport 3 should screen out data from frport 2.

IP Routing

IP routes are statically configured on the LPM. Each LPM supports up to 600 route entries in itsroute table. Each route entry consists of a DESTINATION IP ADDRESS , SUBNET MASK ,NEXT HOP IP ADDRESS , and a METRIC value.

Multiple routes to the same destination IP address may be configured in a route table withdifferent metric values. Metric values between 1 and 15 can be assigned to routes based on suchthings as the routing path speed or the number of hops. The route to a destination IP address withthe lowest metric value is the route chosen if the interface that the route uses is available.


Interface Modules________________Configuring multiple route entries in the route table for a particular destination IP address is usedto establish alternate IP routing.

A default route may also be entered into the route table, where the destination IP address isconfigured as 0.0.0.0. As IP packets are being routed through the LPM, if no other route can befound for a particular destination IP address, the default route is used. These packets are routed tothe next hop specified by the default route entry.

Alternate IP Routing

Alternate IP routes may be configured for a particular IP destination to implement fault tolerantrouting. If the next hop to a destination is through an interface which is currently not available,whether it be a physical LAN port or a virtual frame relay port, the LPM will choose anotherroute if one exists. If an IP destination has multiple routes in the route table, the route that is usedis the one that has both the lowest metric value and has a next hop that is associated with aninterface that is up and available.

IP Addressing

The following list summarizes the restrictions that apply to IP addresses and subnet masksconfigured on the LPM.

IP Addresses

— IP addresses are specified in decimal dot notation. That is, all IP addresses are expressedas I.J.K.L; where: I, J, K, L are integers in the range of 0 to 255.

— The first octet of any IP address must be in the range of 1 to 126 and 128 to 223.

— The address must contain valid host and network portions. That is, the network or subnetportion cannot be all ones or all zeros and the host portion cannot be all ones or all zeros.

— The IP address 0.0.0.0 is allowed as the default route.

Subnet mask

— Subnet masks must have a correct network portion. That is, for a class A network, thenetwork mask must be at least 255.0.0.0; for a class B, at least 255.255.0.0; and for aclass C, at least 255.255.255.0.

— If the subnet mask is not equal to the network mask (a subnet exists) and the mask is notthe host-specific mask (see below) the subnet portion must be at least two bits wide andthe host portion must be at least two bits wide.

— The mask 255.255.255.255 is allowed and specifies a host route. When this mask is usedat least one bit of the host portion of the destination address must be a "1".


Interface Modules________________Additional checking

– No two ports, physical or virtual, on the same module can have the same IP address.

– No two ports can be on the same subnetwork.

– A port cannot have the same IP address as the remote end of a frame relay PVC.

– An LPM port cannot have the same IP address as the destination IP address of a route onthe same LPM.

– An LPM port cannot have the same address as the next hop IP address of a route on thesame LPM.

– The IP address of the remote end of an LPM frame relay PVC must be on the samesubnetwork as its virtual frame relay port and must be a valid host address.

– The IP address of the remote end of a frame relay PVC cannot be the same as its virtualframe relay port.

– The IP address of the remote end of a frame relay PVC cannot be the same as the remoteend of any other PVC.

– The next hop IP address of a route entry is restricted to be on a directly connectedsubnetwork and cannot be the IP address of any of the ports.

– The next hop IP address must be a valid host address.

Backbone Trunk Modules

Use of the LPM introduces certain high performance requirements for networking in particular,the ability to handle the large frame sizes allowed. This results in specific requirements for trunkmodules: some trunk modules are specifically recommended to carry LPM frame relay traffic;others are definitely not allowed.

Recommendations.



The recommended BNS-2000 trunks for T3/E3 speeds are the Trunk-T3A, Trunk-E3A,Trunk-T3S, and Trunk-E3S.

Do not route LPM traffic through Datakit VCS Generic 3.4 or earlier nodes. These nodes donot support the window size negotiation required for LPM frame relay service.


Interface Modules________________MSM

For end-to-end network integrity for asynchronous protocol transport, the Multispeed Module(MSM) supports a GOS5 transmitter, which provides flow control, error detection, andretransmission to recover lost data. For transmissions received, the MSM can handle GOS1 toGOS5 transmitted by other modules.

The MSM supports an aggregate throughput of approximately 900 Kbps; however, all 12 portscan be configured at any specified speed. For example, at 100% utilization in a single direction,12 ports can be supported for speeds of 75 bps to 57.6 Kbps, or 8 ports can be supported forspeeds of 76.8 Kbps to 115.2 Kbps, without exceeding the module aggregate throughput.

MSMs can be configured so the administered sum of the user port speeds exceed the aggregateperformance of the module. This type of configuration is acceptable if flow control is enabled.The MSM will flow control the individual ports down to the module aggregate throughput limit.This type of configuration is also acceptable if a higher level protocol protects against data loss bymaintaining a suitable window of outstanding data. If such a higher level does not exist, data losscan result when MSM buffers overflow. A buffer overflow can only occur when the aggregatecapacity of the module is exceeded, flow control is not configured, and a higher level protocol isnot restricting the data entering the MSM port.

Because the MSM is used for a range of applications including traditional asynchronous echoplexapplications, as well as file transfers, delays do not exceed 250 msec (the sum of the transportdelay of a character and the transport delay of its echo), so users do not experience "type ahead."

Users of Point-to-Point Protocol (PPP), Serial Line Interface Protocol (SLIP), or other higherlevel protocols might want to run without flow control. When running without flow control, theprotocol should be configured on the device attached to the MSM so an outstanding window doesnot exceed the buffering capacity of an MSM port, which is approximately 3,683 bytes.

The MSM interworks with all asynchronous configurations of Data Networking Products nodes;see the Interworking section that follows. The MSM also interworks with the LCS60 NetworkInterface (LCS60) for traditional terminal-to-host traffic, and it passes Serial Line InternetProtocol (SLIP) and Point-to-Point Protocol (PPP) over a serial connection.

The MSM functions in conjunction with the Network Access Control System.

The MSM supports autobaud up to 19.2 Kbps; rates above 19.2 Kbps will not autobaud.

For computer-to-computer asynchronous service, consider using MSM (or SAM) ports rather thanTY12 modules. The MSM and SAM provide error detection and retransmission, while the TY12does not.


Interface Modules________________SYNC8

The Synchronous 8-port Module (SYNC8) is configured in the software as bsc3270.

Terminals connect through control units (CUs) to the SYNC8. When connected to terminal lines,the SYNC8 supports data transfer rates up to 19.2 Kbps, but typically operates at 9.6 Kbps oneight ports through EIA RS-232-C connections. No more than 100 terminals or printers shouldbe connected to a single SYNC8, with no more than 30 on one port.

The limit of 100 3270-type devices depends on average message size and traffic loads. Becausecertain 3270-type devices require large-size transmissions (some color graphics terminals) thenetwork administrator is responsible for not overconfiguring the modules. The limit of 30devices per line ensures a device concentration that provides acceptable bisync performance(independent of network) and line failure recovery time.

Hosts connect directly, or through a DSU or modem, to the module. When connected to a host,data can be transferred at rates up to 56 Kbps over one line with a V.35 connection, or at rates upto 19.2 Kbps over lines with RS-232-C connections.

To administer SYNC8 ports to achieve the best performance, follow these guidelines:

Distribute devices evenly among the CUs, so each CU on a port controls about the samenumber of devices.

Use the lowest possible number of CUs. For example, one CU with ten devices yields betterperformance than two CUs with five devices.

Full-duplex line control yields better performance than half-duplex.

Higher port speed produces better performance.

The following table shows the number of devices per port for a SYNC8, according to the numberof CUs and the port speed. At a port speed of 4800 bps, a maximum of eight CUs can beconfigured on a port; and at a port speed of 9600 bps, a maximum of 11 CUs can be configuredon a port.

TABLE 5-17. SYNC8 Port and CU Combinations

_ ________________________________Number Maximum Devices per Portof CUs

_ _______________________

per Port at 4800 bps at 9600 bps_ _________________________________ ________________________________1 28 32_ ________________________________2 25 52_ ________________________________3 22 47_ ________________________________4 18 41_ ________________________________


Interface Modules________________TABLE 5-17. SYNC8 Port and CU Combinations (continued)

_ ________________________________Number Maximum Devices per Portof CUs

_ _______________________

per Port at 4800 bps at 9600 bps_ _________________________________ ________________________________5 14 36_ ________________________________6 13 32_ ________________________________7 10 27_ ________________________________8 8 23_ ________________________________

9 - 19_ ________________________________10 - 16_ ________________________________11 - 12_ ________________________________

For example, assume that six CUs are being configured with a total of 31 terminals, at a portspeed of 4800 bps:

1. One port with six CUs should not have more than 13 configured devices.

Since there are 31 devices, a second port needs to be configured.

2. Using two ports, allocate the CUs evenly: three CUs on port 1, and three CUs on port 2.

Each port has three CUs. With this arrangement, up to 22 devices can be connected to eachport without exceeding the recommended limit.

3. Each CU should control about the same number of devices. For a near-optimumconfiguration, attach five devices to each controller for a total of 30 devices, and attach thethirty-first device to any controller.

The following table shows one possible arrangement.

TABLE 5-18. SYNC8 Possible Configuration

_ ___________________________________________Control Number of Devices Number of Devices

Unit on Port 1 on Port 2_ ____________________________________________ ___________________________________________CU1 5 5_ ___________________________________________CU2 5 5_ ___________________________________________CU3 5 6_ ___________________________________________


Interface Modules________________TERM32

The TERM32 module is used to support asynchronous and synchronous interfaces on the SAM64and SAM504. It is designed to minimize the possibility of errors during overload. EachTERM32 port has 1827 bytes of buffer available to accept data from a connected device. Oncethe data is accepted, the GOS5 transmitter transmit it reliably across the network. As long as the1827 bytes per port buffer does not overflow, data is not lost.

Asynchronous ports can be configured to support XON/XOFF or EIA flow control. Thus,TERM32 buffers can be protected, provided the external device supports one of these flowcontrol mechanisms. The TERM32 supports a continuous full-duplex flow of data on 24 portssimultaneously at 9.6 Kbps without flow control. It supports a continuous full-duplex flow ofdata on all ports up to 19.2 Kbps with flow control. For half-duplex communications, it supportsall ports up to 9.6 Kbps without flow control and all ports up to 19.2 Kbps with flow controlenabled. TERM32 ports running at speeds less than 19.2 Kbps can use any combination of flowcontrol and 1 or 2 stop bits. Flow control must be enabled for speeds equal to 19.2 Kbps.

As a synchronous interface, the TERM32 serves as the interface between the protocol of theexternal device and the internal packet protocol, providing buffering and data flow control. Iteffectively transmits frames in a full-duplex environment where the communications lines operateat an occupancy of 95% at 9.6 Kbps. If a synchronous device continuously streams data into aTERM32 port, eventually receiver overruns may occur as the module runs out of buffers. Thisrarely occurs with applications using TERM32s because protocol flow control mechanisms andhost processing time provide delays that reduce line occupancy. If overruns do occur, theprotocol error recovery procedures will recover lost data. Users should set flow controlmechanisms within the protocols to limit the amount of data sent to the TERM32 and thuseliminate buffer overruns.


Interface Modules________________TSM8

The Transparent Synchronous Module 8-port (TSM8) supports a variety of synchronous protocolinterfaces, providing data buffering and flow control. It effectively transmits frames in a half-duplex or full-duplex environment where the communications lines operate at an occupancy of95% at 9.6 Kbps and 92% at 19.2 Kbps.

At speeds of 48 Kbps, only the DTE version can be configured; and at 48 Kbps and higher, oneport can be configured. DDCMP is supported up to speeds of 56 Kbps. At 56 Kbps, pipeliningshould not be configured.

If a synchronous device continuously streams data to a TSM8 port, receiver overruns mayeventually occur as the module runs out of buffers. This situation rarely occurs with applicationsusing TSM8s because protocol flow control mechanisms and host processing time provide delaysthat reduce the line occupancy. If overruns do occur, host protocol timers may need to beadjusted for performance. The network’s internal protocol is efficient at delivering data correctly.When host protocols start retransmitting before the network protocols have an opportunity towork, buffer overflows and duplicate data may interrupt the normal operation of the networkprotocols, leading to poor performance. Retransmission timers should be configured for at leastfive seconds, and seven seconds or more may be needed.

Host protocol frame sizes and windows may have to be adjusted to carry data over TSMinterfaces efficiently. TSMs have limited buffer spaces into which they must accept and storebursts of frames. If hosts burst beyond this buffer capacity, end-to-end retransmissions arerequired, causing poor performance and possible failure of the application.

Special consideration must be given to TSM8 synchronous and asynchronous connections.

Although the TSM8 is primarily used for synchronous service, it does support asynchronousdevices. Because the TSM8 does not handle the dialstring for switched calls, it supports onlyPDD calls from asynchronous endpoints. Note the following restrictions on configuring this typeof port.

A TSM8 supports only PDD calls originating from asynchronous endpoints, although theycan be destinations for switched calls from other asynchronous endpoints (such as dial-in callsto a host).

The endpoints can be permanently active ports, but they do not need to be.

Flow control is not a configurable option for a PDD. If the endpoint uses EIA flow control, itis supported. XON/XOFF flow control is not supported.

Nearly full interworking between the synchronous interfaces on the TSM8 is supported across allreleases.


Interface Modules________________TSM-T1

The Transparent Synchronous Module-T1 (TSM-T1) provides synchronous services at highspeeds. To reach the desired levels of service performance, several configuration options must bebalanced.

Network Load

The first step in network engineering is determining how much load the TSM-T1s and trunks areexpected to handle. Calculate the load at the interfaces to the TSM-T1 by considering theanticipated user data rate, the frame size, and the protocol overhead.

Consider the following SDLC/HDLC example. Assume that the average user data rate is 200Kbps. For a frame with 254 bytes of user data and 6 bytes of SDLC/HDLC overhead*, theestimated load on the TSM-T1 is

254 bytes(254 bytes + 6 bytes SDLC/HDLC)_ ____________________________ × 200 Kbps = 204 Kbps

For a frame with 1022 bytes of user data and 6 bytes of SDLC/HDLC overhead, the estimatedload on the TSM-T1 is

1022 bytes(1022 bytes + 6 bytes SDLC/HDLC)_ _____________________________ × 200 Kbps = 201 Kbps

Minimum Number of Modules Needed

To determine the minimum number of TSM-T1s needed to handle the estimated load, refer to thefigure showing module throughput as a function of frame size.

In general, the capacity of one TSM-T1 is an aggregate throughput of 1.536 Mbps. The figureshows the maximum module throughput attainable as a function of frame size.

________________

* This is for modulo 8 formatted frames and includes the 2 frame-delimiting flag bytes; for modulo 128 formattedframes, use 7 bytes of overhead.



100% T1

50% T1

25% T1

1728K

1536K

1344K

1152K

960K

768K

576K

384K

600

90% T1

1200 1800 2400 3000 3600 4200 4800

bytes/frame

bits

/sec

192K

120% T1

80% T1

FIGURE 5-4. TSM-T1 Module Throughput as a Function of Frame Size

NOTE: These numbers assume at least two active ports on the module share the load oftransmitting and receiving frames onto the line. These reflect the limits of the modulealone, and do not factor in such performance variables as windowing limits or thelimits resulting from forcing a single port to handle all the data transfer.


Interface Modules________________The graph illustrates that the larger the frame size, the higher the attainable throughput. Forframe sizes less than 1500 bytes, throughput increases dramatically as the frame size increases.Beyond 1500 bytes, the incremental increase in throughput levels off. See the TSM-T1Engineering for Throughput section for more details.

Number of Ports

Although the TSM-T1 provides four physical interfaces, the number of active ports that can besupported depends on the capacity of the module for a given frame size and the average port use.The capacity of the module can be estimated from the graph showing module throughput as afunction of frame size. The port use can be estimated from the line speed, the speed at which theport is clocked (basing it on the line speed is a worst-case example, since the port is unlikely to bereceiving data continuously).

For example, according to the graph, the module capacity is approximately 1585 Kbps for a framesize of 600 bytes. The following table shows the number of TSM-T1 ports that can be used on asingle module, given the average amount of traffic each port must handle.

TABLE 5-19. Average Traffic per Port and Number of Ports for TSM-T1

_ ____________________________________________________Average Port Throughput (in Kbps) Number of Ports Available_ _____________________________________________________ ____________________________________________________

1536 1_ ____________________________________________________768 2_ ____________________________________________________512 3_ ____________________________________________________384 or less 4_ ____________________________________________________


In general, backbone trunk speeds should be faster than access line speeds. Look at the expectedload during peak traffic periods, and allow for bursts of traffic which exceed that level. It isimportant to make this allowance, to prevent a buildup of queues in the network. The load onbackbone trunks should be monitored continually.

Backbone Trunk Modules

The TSM-T1 provides enhanced synchronous capabilities, such as high port speeds, support forGOS3, and large frame sizes up to 8 kilobytes. These capabilities require great care in selectingthe appropriate trunks.

To support TSM-T1 traffic, the SWT, SFT, Trunk-T1, or Trunk-T3 (CONS/CLNS) are required.The type of trunk that best suits any particular application depends on several factors, includingtraffic load, traffic pattern, number of trunk channels needed, GOS, and frame size.


Interface Modules________________The recommended trunk for speeds from 56 Kbps to E1 is the SWT or the Trunk-PQ. TheSWT and Trunk-PQ have the most internal buffer space of any of the other supported trunks.This attribute may be useful when using GOS3 since the size of the messages coming into thetrunk is at least as large as the end device’s frame size. The number of such frames is limitedonly by the end device’s transmission window.


The recommended trunk for speeds from T3 to E3 is the Trunk-T3 and Trunk-E3, which aresupported on BNS-2000.

Port Configuration Options

This section explains how performance may change with certain configuration options.

Line Speed

The line speed of the port must be configured to match that of the connected data communicationsequipment (DCE) for data transfer to operate smoothly. Determine the estimated busy hour loadand add to it the SDLC/HDLC overhead. If the TSM-T1 is used to transparently carry otherHDLC-based traffic (for example, Transmission Control Protocol/Internet Protocol [TCP/IP]),then add overhead for the other protocols. The sum of all protocol overhead must be included inestimating the offered load. Provision an access line rate that allows for bursts of traffic 20% to30% above the average busy hour offered load.

Minimum Interframe Delay

Minimum interframe delay allows devices that cannot handle back-to-back frames to talk toTSM-T1 ports. See the vendor documentation for any potential device limitations.

This delay configuration option is specified in microseconds (µsec) and is the minimum amountof time a TSM-T1 port waits before transmitting the next frame. The port transmits idlecharacters while it is waiting. The number of µsec specified is a minimum and the actualinterframe delay may become slightly larger than the configured minimum as the offered loadapproaches T1. While allowing a greater variety of devices to talk to the TSM-T1, increasinginterframe delay also decreases throughput.

The calculations below indicate how interframe delay, number of idle characters, and their effecton throughput are related:

interframe delay: number of microseconds (µsec) between frames transmitted ontothe line


Interface Modules________________idle characters: number of mark (0xff) or flag (0x7e) characters sent during the

interframe delayline speed: number of bits/second that can be sent on the line as determined by the clock

on the connected DCE

idle characters = line speed (bits/second) ×8 bits1 byte_ _____ × interframe delay (µsec) ×

1,000,000 µsec1 second_ ____________

% throughput decrease =10,000

interframe delay (µsec)_ ___________________

For example, with a line speed of 512 Kbps, an interframe delay of 5000 µsec reduces throughputby at least 0.5% and introduces at least 320 idle characters between frames.

Broadcast

Broadcast is a multibridging option that allows a host to talk to more than one control unit (CU),by sending messages from the host to all connected CUs at the same time.

The TSM-T1 supports up to 200 configurable broadcast channels, with a maximum of 50channels per port. However, the number of active channels and frame size combinations arelimited by the buffer capacity on the module. Up to the standard frame size of 256 bytes, and awindow size of up to 7 frames, a maximum of 110 channels per module are supported.

For different frame sizes and windows, calculate the number of active channels as follows:

number of active channels = 110 × 304

frame size_ ________

window

7_ _______ ___________

Some examples for a window size of 7 appear in the following table.

TABLE 5-20. TSM-T1 Frame Size and Number of Broadcast Channels

_ _____________________________Frame Size Number of(in bytes) Broadcast Channels_ ______________________________ _____________________________

256 110_ _____________________________512 55_ _____________________________

1024 36_ _____________________________


Interface Modules________________The consequences of high buffer use are congestion and lost data. If more than the recommendednumber of channels are needed, try distributing the channels of one port onto another module.

NOTE: Buffer use can also increase for other reasons such as flow control in the network, lostdata or acknowledgments across noisy trunks, or propagation delays in the network.This would cause the TSM-T1 to queue ingress data on the module. The morebroadcast channels in use that experience flow control, the greater the danger ofcongestion.

If the guidelines above for the number of supportable channels are followed but congestion stilloccurs, make sure the network is not being overloaded elsewhere. For other possible imbalancesin the network, see the TSM-T1 Network Performance section. For information on calculatingdelay, see the TSM-T1 Engineering for Delay section.

Fanout

Fanout is a multibridging option that allows a host to talk to multiple CUs, one at a time.Messages with specific station addresses are sent to and accepted by CUs that are configured forthose addresses.

The TSM-T1 supports up to 50 channels per fanout port, for a total of 200 per module. Hostsmust be configured to poll a maximum of 50 different addresses. CUs must be configured withdifferent addresses; this means that only one CU can respond to a given poll from the host.

To reduce the possibility of congestion, it is recommended that one host port be brought up at atime. When the host polls for the first time, the TSM-T1 broadcasts the message to all channelswith existing calls up to see which CU responds to which address. This enables the TSM-T1 tocreate a map associating the correct channel number with the address the host is polling.Bringing up one host port at a time eliminates the possibility of congestion caused bysimultaneous broadcasts onto as many as 200 channels.

After the address/channel mapping is established, the throughput achievable with fanout for agiven frame size and line speed is within a few percent of the throughput that is achievable withpoint-to-point. For example, with 256-byte frames and a line speed of 256 Kbps, throughput forfanout is about 96% of 256 Kbps.


Interface Modules________________GOS

Two types of GOS — GOS3 and GOS5 — are available on the TSM-T1. The selection of theGOS for the TSM-T1 affects user throughput and the reliability of data transport.

GOS5 provides flow control, error detection and error recovery. In general, GOS5 ispreferred for intra-nodal traffic because it provides error recovery and better performance.GOS5 can still be selected for internodal traffic if the needed throughput is within theperformance limits indicated by the following graphs, which provide a reference forcomparing the effects of an intervening trunk without propagation delay (a trunk of negligiblelength) and a trunk with propagation delay.

GOS3 is considered the transparent mode since it does not provide flow control or errorrecovery. Corrupted blocks are detected and thrown away, but lost data is not retransmittedby the network. There is no transmit window to limit the data in transit; this allows greatermodule throughput when data must traverse long-distance trunks, since there is no window forpropagation delay to close.

GOS3 is preferred for internodal traffic, especially over distances greater than 500 miles.Since the GOS3 does not provide flow control and error recovery, GOS3 should only be usedif the native protocol on the end devices provides the flow control and error recovery,expected error rates of intermediate trunks are low, or if the loss of data is acceptable.

Caution must be used with GOS3 because of the potential load a GOS3 transmitter can placeon trunks in the network. The trunks must be able to handle the instantaneous load offered bythe end device. Furthermore, in competition for trunk resources with GOS5 channels, GOS3channels will tend to dominate as GOS5 windows close and retransmission is delayed whileGOS3 channels continue to transmit.


Interface Modules________________GOS 5 (Intra-node)

GOS 3 (Intra-node) 80% T1

GOS 3

70% T1

50% T1

20% T1

GOS 5

(555)540

480

420

360

300

240

180

120

60

Trunk LengthPropagation Delay

0 mi0 ms

500 mi4 ms

1000 mi8 ms

1500 mi12 ms

2000 mi16 ms

2500 mi20 ms

3000 mi20 ms

3500 mi28 ms

4000 mi32 ms

Fra

mes

/sec

FIGURE 5-5. TSM-T1 GOS3 and GOS5 Performance Over Trunks (300-byte Frames)



GOS 5 (Intra-node)GOS 3 (Intra-node)

80% T1

GOS 3

50% T1

20% T1

GOS 5

180

160

140

120

100

80

60

40

20

Trunk LengthPropagation Delay

0 mi0 ms

500 mi4 ms

1000 mi8 ms

1500 mi12 ms

2000 mi16 ms

2500 mi20 ms

3000 mi20 ms

3500 mi28 ms

4000 mi32 ms

Fra

mes

/sec

FIGURE 5-6. TSM-T1 GOS3 and GOS5 Performance Over Trunks (1000-byte Frames)

Buffer Flushing

Buffer flushing lowers the incidence of duplicate frames that arise from simultaneous GOS5 andend device error correction retransmissions by discarding queued data in the TSM-T1s. It isuseful for higher level applications that cannot recover from duplicate frames and end upterminating the session. Buffer flushing is configurable for point-to-point configurations. It issupported on the TSM-T1 to provide interworking capability with TSM8s and SAMs that areconfigured with buffer flushing. Other options are discussed below.

When a circuit becomes flow controlled, as a result of noise, congestion, or speed mismatching,the end device may time out awaiting acknowledgment and retransmit frames.


Interface Modules________________With GOS5, if the TSM-T1 does not receive an acknowledgment, the TSM-T1 will alsoretransmit. When the flow control condition clears, duplicate frames arrive at the end device.Buffer flushing does not guarantee that all duplicate data will be discarded in all situations, but itminimizes the occurrence while still allowing for GOS5 retransmissions where necessary.

Since data is discarded during a buffer flush, it can have an adverse effect on throughput. Usebuffer flushing only if the following suggestions do not alleviate the problem:

Increase the host acknowledgment timer to 4 or more seconds to avoid having both the hostand TSM-T1 time out and retransmit. This higher host timer allows the TSM-T1 to time outfirst and retransmit.

However, be aware that increasing the host timer also increases the host’s error recoverytimes.

Transport delay should be included in the host timeout value; see the TSM-T1 Engineeringfor Delay section.

In speed mismatching, the extra time needed for the slower device to transmit should be addedto the host timeout value and/or the host transmission window should be limited if possible.

Use GOS3 since there are no retransmissions. Read the Grade of Service section before usingthis option. However, be aware that GOS3 does not overcome duplicate frames arising fromend device retransmissions. If data is delayed in a congested or noisy network, causing thehost to time out and retransmit, the other end can still receive duplicate frames when thecongestion clears and data starts moving again. GOS3 only ensures that the duplicate framesdo not come from the TSM-T1.

As an example of a mismatch in speed, consider the following. If the frame size is 256 bytes perframe and the window is 127, then the transmission window of the front-end processor (FEP) is

frame256 bytes_ ________ ×

transmission window127 frames_ _________________ =

transmission window32,512 bytes_ _________________

A 256 Kbps FEP can transmit 32,512 bytes in approximately

second256,000 bits_ __________ ×

8 bits1 byte_ _____ ×

32,512 bytes1 transmission window_ ___________________ = 1 second

A 64 Kbps cluster controller can transmit 32,512 bytes in approximately

second64,000 bits_ _________ ×

8 bits1 byte_ _____ ×

32,512 bytes1 transmission window_ ___________________ = 4 seconds

In this case, the host timer should be increased by three seconds.

Alternatively, try limiting the host transmission window because the less data the slower portmust contend with, the smaller the time discrepancy for transmission between the slower clustercontroller and the faster host.


Interface Modules________________TSM-T1 Network Performance

This section examines factors that affect the dynamic performance of TSM-T1 operations andapplies to both multibridged (fanout and broadcast) and point-to-point applications. It providessome guidelines and calculations for determining such performance parameters as throughput anddelay. These calculations assume that only TSM-T1s are connected to the end devices.

In using this section, remember that the user’s perceived throughput is not the same as the totalload the TSM-T1 must handle. Application data is passed as blocks of data through multiplelevels in the protocol stack before it gets to the TSM-T1 port. At each successive level,additional protocol overhead may be added, increasing the total load that the TSM-T1 must passthrough the network. This reduces the user’s perceived level of throughput. Processing delays,handshaking, acknowledgments, and other factors can further reduce the user’s perceived level ofthroughput.

As an example of the effects of protocol overhead, consider a SDLC frame with 254 bytes of userdata and 6 bytes of SDLC overhead for a modulo 8 formatted frame. The SDLC overhead is 6bytes.

(254 + 6 bytes)254 bytes_ ____________ = 97.6%

The user’s perceived throughput is 97.6% of the network throughput. Processing delays,handshaking, acknowledgments, and other factors reduce this further.

Consider the effect of delay on throughput. At 1.536 Mbps, 192 idle characters can be sent in 1millisecond. Therefore, for every millisecond of delay that may exist between frames, it is as if192 bytes of overhead were added to every frame transmitted. Hence, delay also lowersthroughput. See the TSM-T1 Engineering for Delay section for the factors that add to delay.

TSM-T1 Engineering for Throughput

Throughput is one performance characteristic that could be estimated. Throughput can measurehow efficiently the TSM-T1 is being used and can also indicate performance problems in thenetwork.

The following graph shows the relationship between frame size and the maximum attainablethroughput for a single port on the TSM-T1 for GOS3 and GOS5.



90% T1GOS 3

50% T1

20% T1

GOS 51536K

1344K

1152K

960K

768K

576K

384K

192K

600

80% T1

1200 1800 2400 3000 3600 4200 4800

bytes/frame

bits

/sec

FIGURE 5-7. Intranodal Point-to-Point TSM-T1 Throughput as a Function of Frame Size

In general, GOS5 provides higher throughput than GOS3 for small frames in an intra-nodalconfiguration. As the frame size approaches 2700 bytes, the throughput achievable with GOS3approaches that of GOS5. For frames larger than 2700 bytes, the throughput appears to be thesame for both levels of GOS. This is true for frame sizes up to 6000 bytes (frames larger than4800 bytes do not appear in the graph). For frames larger than 6000 bytes, throughput decreasesto less than 1 Mbps. Therefore, frames beyond 6000 bytes should only be used to satisfy theparticular requirements an end device may have, not to achieve greater throughput.


Interface Modules________________NOTE: The higher throughput attainable with GOS3 applies to internodal configurations where

the longer the trunks, the greater the throughput advantage of GOS3 over GOS5.GOS5 is recommended for intra-nodal configurations.

For fanout ports, the maximum attainable throughput is close to that for point-to-point; see thefollowing figure.

For broadcast ports, the greater delay incurred from having to send frames onto every activechannel on the port lowers throughput. In general, delay and throughput are inverselyproportional: the higher the delay, the lower the throughput, and vice versa.

The following provides a rough estimate of the throughput for a particular broadcast channel.

per channel throughput: number of bytes per second a particular broadcast channelcan transmit

frame size: number of bytes in the framebroadcast delay: number of seconds needed to transmit 1 frame (frame size)

per channel throughput (bytes/second) =broadcast delay (seconds)

frame size (bytes)_ _____________________

For a typical frame size of 256 bytes, the broadcast delay numbers given in Table 5-19 can beused in this equation. Consider the 12th broadcast channel of a port receiving a 256-byte frame.This channel has a throughput of

0.055 seconds256 bytes_ ___________ = 4,654 bytes/second

For other delays that can affect throughput, see the TSM-T1 Engineering for Delay section.

TSM-T1 Engineering for Delay

Two kinds of delay must be distinguished in planning:

Transport delay is the time measured from when the first character leaves the customer’stransmitting end device to when the last character enters the customer’s receiving end device.

Network transport delay is the time measured from when the first character enters the networkto when the first character leaves the network. Network transport delay is roughly theadditional delay introduced by the presence of a network, as opposed to the delay from aprivate line connection.

Either transport or network delay is one performance characteristic to estimate. For example,transport delay may be a parameter to consider in setting host timeout values. There are also twodistinct types of traffic with different delay requirements that should be considered:

file transfers

terminal-to-host sessions


Interface Modules________________Acceptable performance for terminal-to-host character echoplexing usually requires round-tripdelays of no more than 200 to 250 msec. When setting host timeout values, be sure to considertotal transport delay. Since higher delays result in lower throughput, delay is also a usefulparameter to know in examining throughput.

TSM-T1 Network Transport Delay. When calculating the total network transport delay,consider the individual delays introduced by the following:

TSM-T1 port access/egress delay

TSM-T1 processing delay

backplane delay (negligible)

trunk processing delay

trunking delay

trunk propagation delay

DSU/CSU or modem processing delay

The remainder of this section steps through each of these delays, with accompanying numbers toestimate transport and network delay. As with all the measurements provided in this chapter,these are best case examples. Your own measurements will vary, but use these as a starting pointfor estimating delay.

Port Access/Egress Delay

Access/egress delay for a port or any device is the time it takes to clock in/out the datafrom/onto the line and is a function of the amount of data to be clocked and the line speed.

To calculate the access or egress delay for a single frame, convert the frame size from bytes tobits and divide by the line speed in bps:

access/egress delay: number of seconds to clock a frame in/out of the portframe size: number of bytes in the frame including SDLC/HDLC overhead

access/egress delay (seconds) = (frame size [bytes] + 2 flag [bytes]) ×line speed (bps)

8 bits/byte_ _____________

TSM-T1 Processing Delay

Next, calculate the processing delay for the TSM-T1. This delay comprises ingress delay,backplane delay (which is negligible), and egress delay. Use the tables on point-to-point andfanout or broadcast processing delays. These measurements are the total of backplane,module ingress, and module egress processing delays.


Interface Modules________________TABLE 5-21. TSM-T1 Processing Delays

_ ___________________Frame Size Delay

(bytes) (msecs)_ ____________________ ___________________128 3_ ___________________256 3_ ___________________512 4_ ___________________

1024 7_ ___________________1500 9_ ___________________2000 12_ ___________________2500 14_ ___________________

The following table lists the delay in milliseconds for broadcast using a typical frame size of256 bytes. The delays shown were measured for a case where the last channel on the port isthe channel that responded to the broadcast.

For example, if there are 12 broadcast channels on the port, and the twelfth channel responds,the amount of time it takes for the 256-byte frame to go from ingress into the broadcast port,across the backplane on the twelfth channel, and out the egress port at the remote end isapproximately 13 milliseconds.

TABLE 5-22. TSM-T1 Broadcast Delays

_ ________________________Number of BroadcastChannels Delay (msecs)_ _________________________ ________________________

1 3_ ________________________12 13_ ________________________25 20_ ________________________37 35_ ________________________50 55_ ________________________

Trunk Processing Delay

Next, add the trunk processing delay. Double the delay since there are two trunk modules forevery trunk. The following table lists approximate delays based on the type of trunk and itslevel of use. Low, medium, and high correspond to 20%, 40%, and 60% trunk use,respectively.


Interface Modules________________TABLE 5-23. Trunk Processing Delays for a TSM-T1

_ ____________________________________________________________Delay (msecs)*_ _______________________________________________

TrunkLow Utilization Medium Utilization High Utilization_ _____________________________________________________________ ____________________________________________________________

SWT

(56 Kbps) 8(2) 13(3) 34(5)

(256 Kbps) 2(1) 3(1) 7(2)

(DS-1) 1_ ____________________________________________________________Trunk-T1 (DS-1) 1_ ____________________________________________________________Trunk-HS 1_ ____________________________________________________________SFT 1_ ____________________________________________________________

* The delays shown in parentheses were gathered for very small, high priority messages,such as echoplex traffic.

Trunking Delay

Next, add the trunking delay. This is the time it takes the trunk to clock out/in the data ontothe trunk. This is a function of the line speed and the amount of data. Since there is trunkingoverhead in each trunk frame, that must be added to the frame size. As a rough estimate, usea factor of 1.2:

trunking delay: number of seconds to clock a frame onto/off the trunkframe size: number of bytes in the frame including SDLC/HDLCoverhead:

trunking delay (secs) = 1.2 × (frame size [bytes] + 2 flag [bytes]) ×line speed (bps)

8 bits/byte_ _____________

Trunk Propagation Delay

Next, calculate the propagation delay through the network trunks, which is proportional to thedistance traveled:

propagation delay = 8 msec per 1000 miles one way

DSU/CSU or Modem Processing Delay

Add the processing delay for any DSU/CSUs or modems in the network. This is 1millisecond or less for DSU/CSUs at speeds greater than 56 Kbps.

The sum of these delays is the estimated total one-way network transport delay. To calculatethe round-trip delay for fanout or point-to-point, double the one-way delay.

To calculate the round-trip delay for broadcast, add the return trip delay to the broadcastdelay. The return trip delay is the same as that for point-to-point or fanout.


Interface Modules________________For example, using the tables on broadcast processing and point-to-point and fanoutprocessing delays, for the twelfth channel sending and receiving a 256-byte frame, the round-trip module and backplane processing delay is approximately:

round-trip delay for 12th broadcast channel = 13 msecs + 3 msecs = 16 msecs

As an example, in calculating network transport delay, consider a frame of 1506 bytes sent ina point-to-point configuration:

(1506 + 2) × 8 bitsaccess/egress delay = _ _____________

1536 Kbps

= 7.8 msec

TSM-T1 processing delay = 9 msec

trunk processing delay = 2 msec

1.2 × 1506 × 8 bitstrunking delay = _ _____________

1536 Kbps

= 9.4 msec

propagation delay = 8 msec

total network delay = 36.2 msec

TSM-T1 Transport Delay. For total transport delay, there are two access/egress times: oneaccess time in entering the network and one egress time in exiting the network. In the aboveexample, this is 7.8 milliseconds. The total transport delay is then

36.2 milliseconds + 7.8 milliseconds = 44 milliseconds

The network only introduces a delay of 36.2 milliseconds.

When calculating round-trip delay times, consider the processing time for the end devices:

host processing delay

control unit processing delay

NOTE: The examples cited in these sections cannot cover every possible network configurationwhere there may be different numbers and/or types of equipment, each with their owndelay characteristics. In addition, if there is congestion and queueing delay in thenetwork, the total delay will increase.


Interface Modules________________TSM-T1 Network Efficiency. Network efficiency, as a function of the delay introduced by thenetwork, can be estimated for the data transfer of a series of frames. That is, how long does ittake the first frame entering the network to exit the network when it is followed by 6 other frames.Consider the transfer of seven 1506-byte frames. The network delay for a single 1506-byte framewas calculated above as 36.2 milliseconds. Consider whether this changes for a series of framessent at one time. Each frame can be at a different point along the network path so that before oneframe exits the network there can be other frames already in the pipe:

(7 × [1506 + 2] × 8 bits)total access/egress delay

_ __ _ _ ___________________1536 Kbps

= 55 msec

The transport delay is determined by

(Ttotal

- T0) .

But remember that a connection between two end devices connected without an interveningnetwork also has a total egress delay of 55 milliseconds. The delay that is introduced by thenetwork for the sequence of frames is then only

(Tnetwork

- T0)

This is the same as the additional delay for one frame: 36.2 milliseconds.



5432

INGRESSPORT

ARRIVAL

. . . . . . . .NetworkDelay

1

..........................................

7

.....................................................

TrunkingDelay

Egress Delay

6

Access Delay

Trunk PropagationDelay

Trunk ProcessingDelay

TSM-T1 ProcessingDelay

54F

7

F3

FF2

F

6

F1

F

FFF

Frame AccessDelay

F

Total

F

..........................................

F

Total

F

T0

Ttotal

EGRESSPORT

TRANSMIT

Tnetwork

TIME

FIGURE 5-8. Network Transport Delay via a TSM-T1 for a Window

At 1.536 Mbps, 192 bytes can be sent in 1 millisecond. A delay of 36.2 milliseconds can beviewed as equivalent to 6950 overhead bytes. The data received on ingress is 10,556 bytes, so theefficiency in the network is

(10556 + 6950 bytes)10556 bytes_ _________________ = 60.2%

The effective bandwidth is

0.602 × 1536 Kbps = 925 Kbps

The user perceived efficiency was estimated as 97.6% of the network throughput, so the userperceived throughput is

0.976 × 925 Kbps = 903 Kbps

This is the maximum throughput that can be expected through the network; factors such ascongestion can further increase delay and decrease throughput. The average throughput over timemay be greater or lower, depending on how and when the window reopens.


Interface Modules________________Besides the one-way delay calculated here, the return delay would also be calculated to determinewhen the window would reopen.

Interworking

The TSM-T1 interworks with the Transparent Synchronous Module 8-port (TSM8); however,calls originating from a TSM8 through a Datakit II VCS, Release 1.0, node to a TSM-T1 are notsupported.

The TSM-T1 interworks with the SAMs. TSM-T1 ports that interwork with these devices mustbe configured for GOS5. GOS3 can be used only between TSM-T1 ports. During call setup, ifthe TSM-T1 detects a mismatch in GOS, the call is taken down and a thresholded alarm is issued.If a port configured as a PDD is originating the call, the call setup, takedown, and alarm sequenceis repeated as PDDs retry calls periodically.

NOTE: If calls traverse or terminate at Datakit VCS or Datakit II VCS Release 1 nodes,incompatible GOS levels might not be detected.

The TSM-T1 supports higher throughput than the modules with which it interworks. Therefore,be careful that the TSM-T1 does not overload these modules. The following table indicates thecapacity of these modules.

TABLE 5-24. Module Interworking with a TSM-T1

_ ___________________________________________Module Type Line Speed (in bps)_ ____________________________________________ ___________________________________________

LCS100 Concentrator Module 9,600_ ___________________________________________Synchronous SAM8/SAM16 19,200_ ___________________________________________Synchronous SAM64/SAM504 9,600_ ___________________________________________TSM8 48,000 – 64,000 (one port)_ ___________________________________________


Interface Modules________________TY

The Terminal Module 12-port (TY-12) and Terminal Module 6-port (TY-6) provide basicasynchronous interface support. They differ in the number of ports supported, the interfacespeeds, and the supported throughput.

The TY12 has a total throughput capacity of 115.2 Kbps. It supports up to 12 devices, clocked atspeeds up to 19.2 Kbps, with a simultaneous total data flow from all the devices of up to 115.2Kbps. The following table shows how many devices with continuous data flow can be supportedby the 115.2 Kbps limit of the TY12 module.

TABLE 5-25. TY12 Throughput_ ____________________________________________________________________________

Continuous Number of SimultaneousDevice Speed Data Flow Continuous Data Streams_ ______________________________________

(Kbps) (Kbps) One Way Two Way_ _____________________________________________________________________________ ____________________________________________________________________________≤19.2 4.8 12 12_ ____________________________________________________________________________≤19.2 9.6 12 6_ ____________________________________________________________________________≤19.2 19.2 6 3_ ____________________________________________________________________________

NOTE: Flow control must be enabled for the direction of continuous data flow. If flow controlis not used for the direction of data flow, some means of compensating for the outputdevice running slower than the input device must be used to avoid data loss. Themechanism needs to consider the 256 character maximum internal buffering capacity ofthe asynchronous path.

The TY12 offers GOS1 for more efficient data transmission or GOS2 for flow-controlledtransmission. Retransmission of the data is the user’s responsibility. Losses from GOS1,congestion, or network failures can be detected by end-to-end data transfer protocols, whenprovided.


Interface Modules________________The TY6 has a total throughput capacity of 57.6 Kbps. It supports up to 6 devices, clocked atspeeds up to 19.2 Kbps, with a simultaneous total data flow from all the devices of up to 57.6Kbps. The following table shows how many devices with continuous data flow can be supportedby the 57.6 Kbps capacity limit of the TY6.

TABLE 5-26. TY6 Throughput

_ ____________________________________________________________________________Continuous Number of Simultaneous

Device Speed Data Flow Continuous Data Streams_ ______________________________________(Kbps) (Kbps) One Way Two Way_ _____________________________________________________________________________ ____________________________________________________________________________≤19.2 4.8 6 6_ ____________________________________________________________________________≤19.2 9.6 6 3_ ____________________________________________________________________________≤19.2 19.2 2 0_ ____________________________________________________________________________

NOTE: Flow control must be enabled for the direction of continuous data flow. If flow controlis not used for the direction of data flow, some means of compensating for the outputdevice running slower than the input device must be used to avoid data loss. Themechanism needs to consider the 256 character maximum internal buffering capacity ofthe asynchronous path.


Interface Modules________________X.25

The X.25 module provides basic X.25 interface services consistent with CCITT 1988 standards.Some key planning factors are shown in the following table.

TABLE 5-27. X.25 Planning Factors

_ _______________________________________Characteristic Specification_ ________________________________________ _______________________________________

Services X.25 Switched and X.25 PAD_ _______________________________________Interface Speed 1.2 - 64 Kbps_ _______________________________________Channels (SVC/PVC) 100 maximum_ _______________________________________Packet Size 128 and 256_ _______________________________________Window Size (L3) 1 to 5_ _______________________________________Module throughput 80 Kbps_ _______________________________________Interface Ports 4 RS-232 or

3 RS-232 + 1 V.35 DTE_ _______________________________________

Since the total module throughput is limited to 80 Kbps, only one port can be supported at thehigher speeds.

The X.25 module operates in pass-through mode for connections to other X.25 modules, X.25Pmodules, and X.75 modules. It is capable of transmissions using GOS2 or GOS5, depending onthe X.3 PAD profile configured. A GOS5 profile provides error detection and correction, while aGOS2 profile does not. GOS2 is recommended for echoplexing traffic because of its loweroverhead.


Interface Modules________________X.25P

The X.25P module provides more capabilities and higher performance than the X.25 module. Itprovides basic X.25 interface services consistent with CCITT 1988 standards. Some keyplanning factors are shown in the following table:

TABLE 5-28. X.25P Planning Factors_ _______________________________________

Characteristic Specification_ ________________________________________ _______________________________________Services X.25 Switched and X.25 PAD_ _______________________________________Interface Speed 1.2 - 2048 Kbps_ _______________________________________Channels (SVC/PVC) 507 maximum_ _______________________________________Packet Size 128, 256, 512, and 1024_ _______________________________________Window Size (L3) 1 to 7_ _______________________________________Module Throughput 1 Mbps_ _______________________________________Interface Ports 8 RS-232 or

4 V.35 DTE_ _______________________________________

The 1 Mbps module throughput of the X.25P allows all four ports to operate at speeds up to 64Kbps. Beyond 64 Kbps, the recommended number of ports depends on the packet size. Themodule operates in one of several modes depending on the module at the remote end:

pass-through (pass) mode (an X.25 module and an X.25P module)

PAD (pad) mode (an asynchronous endpoint and an X.25P module)

terminate (fplp) mode (an X.25P module or an X.75 module and an X.25P module)

The X.25P module uses a GOS5 transmitter, which provides error detection and correction.


Interface Modules________________Configuration Options

The following sections explain the options that can be administered for an X.25P module.

X.25P Ports and Interface Speed

The number of usable ports may be limited by the maximum available module throughput (see"Module Throughput"). The following table provides recommended numbers of ports forrepresentative line speeds. For line speeds up to 64 Kbps, port throughput is approximately theline speed. For line speeds up to 512 Kbps, port throughput of 50% of the line speed can beachieved. Beyond 512 Kbps, the port throughput is limited by the total module throughput.

TABLE 5-29. Recommended Number of Ports For Combinations of Line Speed andPacket Size

_ __________________________________Packet Size_ _______________________

Line Speed 128 256 512 1024_ ___________________________________ __________________________________19.2 4 4 4 4

56 4 4 4 4

64 4 4 4 4

128 4 4 4 4_ __________________________________256 2 2 4 4_ __________________________________384 1 2 2 2_ __________________________________512 1 1 2 2_ __________________________________768 1 1 1 1

T1 1 1 1 1

E1 1 1 1 1_ __________________________________


Interface Modules________________X.25P Ports and Number of Logical Channels

The module can support up to 507 user channels, which can be a combination of SVC or PVCchannels. However, the maximum number that can be recommended for any given port dependson the following L3 parameters: default window size, default packet size, maximum windowsize, maximum packet size, packet segmentation, and remote packet size. The followingequations show the relationship of these parameters.

H =i = 1ΣN

C i *2*128

PS i * WS i_ ________

V j =T

507 − H_ ______ *PS j * WS j

2*128_ ________

UC j ≤ min(V j , T1_ _ * (UCM −

i = 1ΣN

C i ) )

H = normalized number of channels already configured for each portC i = number of configured user channels for port iPS i = default packet size for port i; see the Data Networking Products X.25 and X.25P Module ReferenceWS i = default window size for port i; maximum window size for port iT = number of ports that the NA is configuring for the moduleUC j = number of allowable channels for port j, j is one of the ports NA is enteringUCM = number of user channels entered at the module levelN = four or eight; the maximum number of ports on the module

The following table shows recommended channel limits per port based on the values of other L3parameters when the channels are evenly divided among the ports.

TABLE 5-30. Recommended Channels per X.25P Port

_ ___________________________________________________________L3 L3 Number Configurable Configurable

Window Size Packet Size of Ports Channels Channels(WS) (PS) (T) per Port (UC) per Module_ ____________________________________________________________ ___________________________________________________________

2 128 1 507 507_ ___________________________________________________________2 128 4 126 504_ ___________________________________________________________4 128 1 253 253_ ___________________________________________________________4 128 2 126 252_ ___________________________________________________________4 128 4 63 252_ ___________________________________________________________4 128 8 31 248_ ___________________________________________________________4 256 1 126 126_ ___________________________________________________________4 256 4 31 124_ ___________________________________________________________


Interface Modules________________The following table shows the recommended number of configurable channels per moduledepending on L3 window and packet size. It assumes each port is using the same L3 window andpacket size setting. The total recommended number of configurable channels is the sum of thenumber of channels configured for all ports (up to four ports for V.35 connections; up to eightports for RS-232-C connections) and is not the number of channels configured at the modulelevel. The number of channels configured at the module level can be greater than the sum of thechannels configured for all ports.

TABLE 5-31. Recommended Maximum Number X.25P Channels

_ _________________________________Recommended L3 L3

Maximum Number Window Packetof Channels Size Size_ __________________________________ _________________________________

507 2 128_ _________________________________338 3 128_ _________________________________253 4 128_ _________________________________253 2 256_ _________________________________169 3 256_ _________________________________126 4 256_ _________________________________72 7 256_ _________________________________

126 2 512_ _________________________________84 3 512_ _________________________________63 2 1024_ _________________________________16 7 1024_ _________________________________


Interface Modules________________Packet Size

The X.25P module supports network level (level 3) packet sizes from 128 to 1024. Themaximum L3 packet size is configured on a per port basis. When X.25P modules interwork witheach other, one side of the call can have a packet size that differs from the other side of the call.

Administering a larger packet size increases X.25P module throughput. For file transferapplications, larger packet sizes are recommended because of higher module throughput.However, larger X.25 packet sizes decrease the recommended number of logical channelsconfigurable on the module. Larger X.25 packet sizes can also increase response time.

When the X.25P module interfaces to a X.25 module or to an asynchronous endpoint, themaximum L3 packet size provided by an X.25P port is 256 bytes. If the port is configured with amaximum packet size larger than 256, it is negotiated down to a maximum of 256.

TABLE 5-32. X.25P Packet Sizes

_ ____________________________________________________Remote X.25P Maximum Length of

End Communication User Data FieldModule Mode in an L3 Data Packet_ _____________________________________________________ ____________________________________________________

Asynchronous endpoints PAD 256 octets_ ____________________________________________________X.25 module Pass through 256 bytes_ ____________________________________________________

Another X.25P module Terminate 1024 octets_ ____________________________________________________X.75 module Terminate 1024 octets_ ____________________________________________________

Window Size

The X.25P module supports network level (level 3) window sizes from 1 to 7, and link level(level 2) window sizes from 1 to 7 for basic numbering and 1 to 32 for extended numbering. Themaximum window size is configured on a per port basis. The X.25P module allows one side ofthe call to have a window size that differs from the one on the other side of the call.

Choosing a larger window size increases X.25P module throughput. However, larger L3 windowsizes decrease the maximum number of logical channels recommended on the module. A largerwindow size can also increase response time. When interworking with an X.25 module, the X.25and X.25P window sizes must match.

Network Configuration

Module performance is also influenced by the network configuration, particularly by access linespeeds, backbone trunk speeds, and the overall traffic load. Throughput and delay vary with eachconfiguration. The slowest link in each end-to-end path is the critical component for engineeringthat path.


Interface Modules________________Module Throughput

The maximum module throughput depends on line speed, the number of ports in use, and thenetwork-level packet size. The module reaches a maximum throughput for line speeds as low as128 or 256 Kbps, depending on the number of ports and packet size. The following figureportrays the total module throughput for various packet sizes as a function of line speed. Themodule throughput is the sum over all active ports for both directions. The line on the graph foreach packet size shows the maximum throughput for the optimal number of ports. The portvalues are shown in the figure near the data points. The recommended maximum number of portsfor each line speed are presented in "Configuration Options".

512 byte p.s.

256 byte p.s.

128 byte p.s.

BAUD RATE (Kbps)

TH

RO

UG

HP

UT

(K

bps)

128 256 384 512 640 768 896 1024

1000

900

800

700

600

500

400

300

200

100

0

12244 Optimal

Numberof Ports1

1122

4

4

4

4

2

1

11

FIGURE 5-9. X.25P Throughput as a Function of Line Speed (per Packet Size)


Interface Modules________________Port Throughput for Terminate Mode

The maximum port throughput depends on line speed, number of ports in use, and network-levelpacket size. To obtain the results presented here, the offered load is evenly distributed across theactive channels; the resulting throughput is independent of network-level window size.Increasing network-level window size, however, is a method to increase the performance of anindividual channel if the offered load is bursty or a long delay exists in the connection betweenthe X.25 endpoint and the port.

The following two tables show the maximum sustained bi-directional throughput per port interminate mode for V.35 and RS-232-C ports. Testing was conducted with all ports operatingsimultaneously. Tests were run for selected numbers of channels up to the recommendedmaximum number of channels. Port throughput is defined in terms of data packets per second aswell as port utilization as derived from measurement reports (dmeas x25p). For example, for a128 byte packet size, 58 Kbps can be transmitted in each direction simultaneously on all fourports of a V.35 X.25P module, which is approximately 90% of the line speed.

TABLE 5-33. Maximum Sustained Performance of V.35 X.25P Ports

_ ___________________________________________________________Physical Interface V.35_ ___________________________________________________________Line Speed 64 Kbps_ ___________________________________________________________Mode Terminate_ ___________________________________________________________L2 Window Size 7_ ___________________________________________________________L3 Window Size 2_ ___________________________________________________________Data Transport full duplex_ ___________________________________________________________Number L3 Maximum Port Port

of Packet Number of Throughput ThroughputPorts Size Channels (Kbps) (data packet/sec)_ ___________________________________________________________

1 128 507 58 53

1 256 253 60 29

1 512 126 61 15

4 128 126 58 53

4 256 63 60 29

4 512 31 61 15_ ___________________________________________________________


Interface Modules________________TABLE 5-34. Maximum Sustained Performance of RS-232-C X.25P Ports

_ ________________________________________________________Physical Interface RS-232-C_ ________________________________________________________Line Speed 19.2 Kbps_ ________________________________________________________Mode Terminate_ ________________________________________________________L2 Window Size 7_ ________________________________________________________L3 Window Size 2_ ________________________________________________________Data Transport full duplex_ ________________________________________________________Number L3 Maximum Port Port

of Packet Number of Throughput ThroughputPorts Size Channels (Kbps) (data packet/sec)_ ________________________________________________________

1 128 507 17.5 16.5

1 256 253 18 9

1 512 126 18 4.5

8 128 63 17.5 16.5

8 256 31 18 9

8 512 15 18 4.5_ ________________________________________________________

For normal operating conditions, the recommended port utilization is 70% and the recommendedprocessor utilization is 75%. This utilization should allow sufficient unused capacity for bursts indata traffic and the performance of other tasks such as measurements and module administration.These figures are available through dynamic and scheduled measurements reports.

In evaluating module status, a distinction should be made between peak and average utilization.Peak utilization can exceed recommended values without indicating that the module isoverloaded. If, during an iteration of dmeas x25p module, the values for AVERAGE MAINUTIL, PEAK MAIN UTIL, or CURRENT MAIN UTIL exceed 75%, the module may beoverloaded; if the AVERAGE MAIN UTIL exceeds 75%, the traffic should be reduced. If, duringan iteration of dmeas x25p port, the value for PORT UTIL exceeds 70%, the port is overloadedand traffic should be reduced.

The module can achieve the throughput in the following table within the recommended processorutilization except for the 128 byte L3 packet size. A load of 45 Kbps or 41 data packets persecond for a 128 byte L3 packet size should fall within the recommended sustained CPUutilization. The recommended port utilization for a line speed of 64 Kbps is 45 Kbps.


Interface Modules________________TABLE 5-35. Recommended V.35 Throughput for an X.25P Module

_ ________________________________________________________Physical Interface V.35_ ________________________________________________________Line Speed 64 Kbps_ ________________________________________________________Mode Terminate_ ________________________________________________________L2 Window Size 7_ ________________________________________________________L3 Window Size 2_ ________________________________________________________Data Transport full duplex_ ________________________________________________________Number L3 Maximum Port Port


1 128 507 45 41

1 256 253 45 22

1 512 126 45 11

4 128 126 45 41

4 256 63 45 22

4 512 31 45 11_ ________________________________________________________

The module can achieve the throughput in the following table within the recommended processorutilization of 75%. The recommended port utilization at a line speed of 19.2 Kbps is 13.4 Kbps.

TABLE 5-36. Recommended RS-232-C Throughput for an X.25P Module

_ ________________________________________________________Physical Interface RS-232-C_ ________________________________________________________Line Speed 19.2 Kbps_ ________________________________________________________Mode Terminate_ ________________________________________________________L2 Window Size 7_ ________________________________________________________L3 Window Size 2_ ________________________________________________________Data Transport full duplex_ ________________________________________________________Number L3 Maximum Port Port


1 128 507 13.4 12.5

1 256 253 13.4 7

1 512 126 13.4 3.5

8 128 63 13.4 12.5

8 256 31 13.4 7

8 512 15 13.4 3.5_ ________________________________________________________


Interface Modules________________Module Throughput for Packet Assembly and Disassembly

Because more CPU processing is needed for packet assembly than packet disassembly, portthroughput depends on the direction of the data. However, a lower total module throughput canbe expected for PAD mode rather than terminate mode. The following table shows one-waythroughput per port. Note that the transparent profile affords the highest performance.

TABLE 5-37. Maximum Sustained Performance of PAD Ports for an X.25P Module

_ ________________________________________________________________________Physical Interface V.35_ ________________________________________________________________________Line Speed 56 Kbps_ ________________________________________________________________________Mode PAD_ ________________________________________________________________________L2 Window Size 7 (basic)_ ________________________________________________________________________L3 Window Size 2_ ________________________________________________________________________L3 Packet Size 128_ ________________________________________________________________________X.3 Profile Transparent_ ________________________________________________________________________Data Transport One Way (assembly or disassembly)_ ________________________________________________________________________

Packet PacketDirection

Assembly Disassembly_ ________________________________________________________________________Number Throughput Throughput Throughput Throughput

of per Port per Port per Port per PortPorts (Kbps) (data packets/sec) (Kbps) (data packet/sec)_ ________________________________________________________________________

1 53.5 52 53.5 52

2 35 34 53.5 52_ ________________________________________________________________________


Interface Modules________________The packet assembly throughput for two ports requires processor utilization greater than 75%. Tokeep the processor utilization below the recommended 75%, the total module throughput shouldnot exceed 52 data packets/second or approximately 53 Kbps. The recommended port utilizationat a line speed of 56 Kbps is 40 Kbps.

The packet disassembly throughput for two ports falls within the recommended processorutilization. The total module throughput should not exceed 180 data packets per second or 187Kbps to maintain the recommended processor utilization. The recommended port utilization at aline speed of 56 Kbps is 40 Kbps.

TABLE 5-38. Recommended PAD Port Throughput for an X.25P Module

_ _____________________________________________________________________Physical Interface V.35_ _____________________________________________________________________Line Speed 56 Kbps_ _____________________________________________________________________Mode PAD_ _____________________________________________________________________L2 Window Size 7 (basic)_ _____________________________________________________________________L3 Window Size 2_ _____________________________________________________________________L3 Packet Size 128_ _____________________________________________________________________X.3 Profile Transparent_ _____________________________________________________________________Data Transport One way (Assembly or Disassembly)_ _____________________________________________________________________

Packet PacketDirection

Assembly Disassembly_ _____________________________________________________________________Number Throughput Throughput Throughput Throughput

of per Port per Port per Port per PortPorts (Kbps) (data packets/sec) (Kbps) (data packet/sec)_ _____________________________________________________________________

1 40 39 40 39

2 26.5 26 40 39_ _____________________________________________________________________


Interface Modules________________Network Delay

The following table shows the delay in milliseconds measured from the last byte in at the localX.25P to the first byte out of the remote X.25P port. This one-way delay is introduced by thenetwork without trunk delay. (The two ports are located on the same node.) For round-trip delaymultiply by two.

TABLE 5-39. Network Delay as a Function of Packet Size

_ __________________Packet Size Delay

(bytes) (ms)_ ___________________ __________________2 3.2

64 3.4

128 3.6_ __________________130 4.1

192 4.4

256 4.7_ __________________260 5.3

320 5.6

384 5.9_ __________________388 6.5

448 6.9

512 7.3_ __________________

The delay is affected by two factors: the number of bytes and the number of buffers that arerequired to hold the frame; therefore, the behavior is nonlinear. The delay for any size datapacket can be estimated by the following equation:

Delay = 2. 5 + .6 * 128

bytes_ ____

+ .0047 * bytes

ms

Because of the relatively low speed of the V.35 and RS-232-C endpoints compared to the trunkbandwidth (1.544 Mbps for a SWT), trunk delay does not have a significant impact on portthroughput. Trunk delay begins to reduce throughput when it exceeds 60 milliseconds.Throughput falls off by approximately 6% to 10% per 8 milliseconds thereafter. (An 8millisecond delay occurs for every 1,000 miles.)


Interface Modules________________X.75

This section provides guidelines for choosing configuration parameters for X.75 interfaces. Themodule operates in three modes:

When a call is made between an X.25P module and an X.75 module, the module is operatingin terminate (fplp) mode.

When a call is made between an asynchronous endpoint and an X.75 module, the module isoperating in PAD (pad) mode.

When a call is made between an X.25 module and an X.75 module, the module is operating inpass-through mode.

Configuration Options for X.75 Service

The configuration options that affect X.75 module operation are the number of X.75 modules thatare residing in a node or an MPC, the number of configured X.75 ports, the number of logicalchannels configured, and the network-level packet and window sizes. The following sectionsexplain these options.

Number of Ports

The number of usable ports may be limited by the module throughput.

Module Throughput in Terminate Mode

The maximum module throughput depends on line speed, network-level packet size, and networklevel window size.


Interface Modules________________The following table shows the total bi-directional module throughput in terminate mode. Modulethroughput is defined in terms of data packet contents, excluding packet layer and link layeroverhead. The bi-directional module throughput of one port configured for a packet size of 128bytes is 92 Kbps; the one-way throughput is 46 Kbps (92÷2), which is about 80% of the linespeed (56 Kbps).

TABLE 5-40. Bi-directional X.75 Module Throughput in Terminate Mode

_ ______________________________________Mode Terminate_ ______________________________________

Line Speed 56 Kbps_ ______________________________________Window Size 2_ _______________________________________ ______________________________________Number of Packet Module

Ports Size Throughput (Kbps)_ ______________________________________1 128 92

1 256 96

4 128 331

4 256 360_ ______________________________________

If, during an iteration of dmeas x75 module, the values for AVERAGE MAIN UTIL,PEAK MAIN UTIL, or CURRENT MAIN UTIL exceed 75%, the module is overloaded and its throughtraffic should be reduced. If, during an iteration of dmeas x75 port, the value for PORT UTIL

exceeds 90%, the port is overloaded and its through traffic should be reduced.

Module throughput for one-way traffic is typically around 85% of the line speed. However, totalmodule throughput cannot exceed 450 Kbps.


Interface Modules________________Module Throughput for Packet Assembly

Because more CPU processing time is needed for packet assembly, lower maximum throughputshould be expected. The following table shows one-way module throughput for packet assembly.Note that the transparent profile affords the highest performance. The total data load on themodule for packet assembly cannot exceed 60 Kbps.

TABLE 5-41. One-way X.75 Throughput for Packet Assembly

_ ___________________________Mode PAD_ ___________________________

Line Speed 56 Kbps_ ___________________________Window Size 2_ ___________________________Packet Size 128 bytes_ ___________________________X.3 Profile Transparent_ ____________________________ ___________________________Number of Throughput

Ports per Port in Kbps_ ___________________________1 48

4 15_ ___________________________

If, during an iteration of dmeas x75 module, the values for AVERAGE MAIN UTIL,PEAK MAIN UTIL, or CURRENT MAIN UTIL exceed 70%, the module is overloaded and its throughtraffic should be reduced. One method to prevent CPU overloading is to reduce the number ofchannels on each port.


Interface Modules________________Module Throughput for Packet Disassembly

Since much less CPU processing time is needed for packet disassembly, module throughput ishigher than that for packet assembly. However, a lower maximum module throughput can beexpected compared with terminate mode.

The following table shows the throughput for packet disassembly. The total data load on themodule for packet disassembly cannot exceed 220 Kbps.

TABLE 5-42. One-way X.75 Throughput for Packet Disassembly

_ ___________________________Mode PAD_ ___________________________

Line Speed 56 Kbps_ ___________________________Window Size 2_ ___________________________Packet Size 128 bytes_ ___________________________X.3 Profile Transparent_ ____________________________ ___________________________Number of Throughput

Ports per Port in Kbps_ ___________________________1 48.7

4 48.7_ ___________________________

Number of Logical Channels

If all channels on each port have a default packet size of 128 bytes and a default window size of 2,the module can support up to 507 user channels, which can be a combination of SVC or PVCchannels. The number of channels allowed for a port depends on the default packet size, defaultwindow size, and the total number of channels allocated for other module ports. The followingequations show the relationship of these parameters.

H =i = 1Σ4

C i *2*128

PS i * WS i_ ________

V j =T

507 − H_ ______ *PS j * WS j

2*128_ ________

UC j ≤ min(V j , T1_ _ * (UCM −

i = 1Σ4

C i ) )

H = normalized number of channels already configured for each portC i = number of configured user channels for port iPS i = default packet size for port iWS i = default window size for port iT = number of ports that the NA is configuring for the moduleUC j = number of allowable channels for port j, j is one of the ports NA is enteringUCM = number of user channels entered at the module level


Interface Modules________________The following table shows configurable channels per port based on the values of otherparameters.

TABLE 5-43. Configurable Channels per X.75 Port

_ _______________________________________________________Available Window Packet Number ConfigurableModule Size Size of Ports Channels

Channels (507-H) (WS) (PS) (T) per Port (UC)_ ________________________________________________________ _______________________________________________________507 2 128 1 507_ _______________________________________________________507 4 128 1 253_ _______________________________________________________507 4 128 2 126_ _______________________________________________________300 4 256 1 126_ _______________________________________________________

The following table shows the maximum number of configurable channels depending on windowand packet size. It assumes each port is using the same window and packet size setting. The totalmaximum configurable channels is the sum of the number of channels configured for all ports (upto four ports) and is not the number of channels administered at the module level. The number ofchannels administered at the module level can be greater than the sum of the channels configuredfor all ports. (The number of channels administered at the module level should match the totalnumber of channels administered for all ports. It is not necessary to administer ports with themaximum number of configurable channels.)

TABLE 5-44. Maximum Number of Configurable X.75 Channels

_ _____________________________MaximumNumber of

Configurable Window PacketChannels Size Size_ ______________________________ _____________________________

507 2 128_ _____________________________335 3 128_ _____________________________253 4 128_ _____________________________253 2 256_ _____________________________169 3 256_ _____________________________126 4 256_ _____________________________


Interface Modules________________Packet Size

When the X.75 module interfaces to a BNS-2000 VCS or BNS-2000 X.25 module or to anasynchronous endpoint, the maximum packet size supported by the X.75 module is 128 or 256bytes. The packet size is configurable on a per port basis. It is possible to configure the X.75module with packet sizes larger than 256, but the packet size is negotiated down to at most 256bytes.

Choosing a larger packet size increases the throughput of the X.75 module. For file transferapplications, a packet size of 256 bytes is recommended because of higher modulethroughput. However, larger X.75 packet sizes decrease the maximum number of logicalchannels per module. Larger X.75 packet sizes can also increase response time.

Network Level Window Size

The X.75 module supports network-level window sizes from 1 to 7. The window size isconfigurable on a per port basis from 1 to 7. The X.75 module allows the X.75 side of a call tohave a window size that differs from the X.25 side of the call.

Choosing a larger network-level window size increases X.75 Module throughput. For file transferapplications, a larger window size is recommended because of higher module throughput.However, larger window sizes decrease the maximum number of logical channels per module. Alarger window size can also increase response time. When interworking with a BNS-2000 VCSor BNS-2000 X.25 module, the X.25 and X.75 network-level window sizes should match.

Performance Issues

Module performance is influenced by the network configuration, particularly by access linespeeds, backbone trunk speeds, and the overall traffic load. Throughput and delay vary with eachconfiguration. The slowest link in each end-to-end path is the critical component for engineeringof that path. As discussed previously, the packet and window sizes chosen also affect modulethroughput.

Interworking

End-to-end data transport requires module interworking compatibility. Frequently, the dataservices required can be achieved using interfaces provided by several different modules. In thefollowing tables, the interface modules listed beneath the heading DNP Supported <Type>Modules are the current modules supported in Data Networking Products nodes. The interfacemodules listed beneath the heading Interworking Compatibility are currently and previouslysupported modules. Check marks indicate module interworking compatibility; that is, thosemodules that provide the data transport service indicated when used with the module in the leftcolumn.


Interface Modules________________TABLE 5-45. Asynchronous Interworking

_ ____________________________________________________________________________DNP Supported Asynchronous Modules_________________________________________________________

Interworking CPY1 MSM TERM32 TSM8 TY6 TY12Compatibility (SAM) (SAM)_ _____________________________________________________________________________ ____________________________________________________________________________Async

APM (SAM8) √ √ √ √ √ √CPY1 (SAM16) √ √ √ √ √ √MSM √ √ √ √ √ √TERM32 √ √ √ √ √ √TSM8 √ √ √ √ √ √TY6 √ √ √ √ √ √TY12 √ √ √ √ √ √_ ____________________________________________________________________________

CustomerProgrammable

DKAP A A A A A A_ ____________________________________________________________________________MultiplexedHost

CPM-HS √ √ √ √ √ √CPM-422B √ √ √ √ √ √CPMML √ √ √ √ √ √CPMML-HS √ √ √ √ √ √_ ____________________________________________________________________________

Standards

X.25 √ √ √ √ √ √X.25P √ √ √ √ √ √X.75

√

√

√

√

√

√_ ____________________________________________________________________________A = Application dependent_ ____________________________________________________________________________

TABLE 5-46. LAN Interconnect Interworking_ _______________________________________________________

DNP Supported LAN Interconnect ModulesInterworking

_ ___________________________________

Compatibility FRM LPM_ ________________________________________________________ _______________________________________________________LAN Interconnect

FRM √ √FRM-M2 √ √LPM √ √_ _______________________________________________________


Interface Modules________________TABLE 5-47. Multiplexed Host Access Interworking

_ ________________________________________DNP Supported

Multiplexed Host AccessInterface Module

Interworking_ _____________________

Compatibility CPM-HS_ _________________________________________ ________________________________________Asynchronous

APM (SAM8) √CPY1 (SAM16) √MSM √TERM32 √TSM8 √TY6 √TY12 √_ ________________________________________

Customer

Programmable

DKAP A_ ________________________________________MultiplexedHost

CPM-HS √CPM-422B √CPMML √CPMML-HS √_ ________________________________________

Special

E2A √SLM √_ ________________________________________

Standards

X.25 √X.25P √X.75

√_ ________________________________________A = Application dependent_ ________________________________________


Interface Modules________________TABLE 5-48. SMDS Interworking

_ __________________________________________________________DNP Supported SMDS Modules

Interworking_ __________________________________________

Compatibility AI-E1 AI-E3 AI-T1 AI-T3 AI-T3P GAR_ ___________________________________________________________ __________________________________________________________SMDS

AI-E1 √ √ √ √ √ √AI-E3 √ √ √ √ √ √AI-T1 √ √ √ √ √ √AI-T3 √ √ √ √ √ √AI-T3P √ √ √ √ √ √GAR √ √ √ √ √ √_ __________________________________________________________

TABLE 5-49. Special Purpose Interworking

_ ______________________________________________________DNP Supported Special Purpose Modules

Interworking_ __________________________________

Compatibility E2A SLM_ _______________________________________________________ ______________________________________________________Multiplexed Host

CPM-HS √ √_ ______________________________________________________


Interface Modules________________TABLE 5-50. Standards Interworking

_ ___________________________________________________________________DNP Supported Standards Modules

Interworking_ _______________________________________________

Compatibility X.25 X.25P X.75_ ____________________________________________________________________ ___________________________________________________________________Asynchronous

APM (SAM8) √ √ √CPY1 (SAM16) √ √ √MSM √ √ √TERM32 √ √ √TSM8 √ √ √TY6 √ √ √TY12 √ √ √_ ___________________________________________________________________

Customer

Programmable

DKAP A A A_ ___________________________________________________________________Multiplexed Host

CPM-HS √ √ √CPM-422B √ √ √CPMML √ √ √CPMML-HS √ √ √_ ___________________________________________________________________

Standards

X.25 √ I I

X.25P I √ √X.75

I

√

_ ___________________________________________________________________A = Application dependent

I = Interworks with constraints_ ___________________________________________________________________


Interface Modules________________TABLE 5-51. Synchronous Interworking

_ ___________________________________________________________DNP Supported Synchronous Modules

Interworking_ ________________________________________

Compatibility CPY1 TERM32 TSM8 TSM-T1 SYNC8_ ____________________________________________________________ ___________________________________________________________Customer

Programmable

DKAP A A A A A_ ___________________________________________________________Synchronous

APM (SAM8) √ √ √ √CPY1 (SAM16) √ √ √ √TERM32 √ √ √ √TSM8 √ √ √ √TSM-T1 √ √ √ √_ ___________________________________________________________

Bisynchronous

SYNC8

√_ ___________________________________________________________A = Application dependent_ ___________________________________________________________


Interface Modules________________Electrical Specifications

The following tables provide electrical information that is important when selecting a node siteand when populating a node with interface modules.

When planning a node site, adhere to the service requirements shown in the following table.

TABLE 5-52. Interface Module and I/O Board Electrical Service Requirements

_ ____________________________________________________________________________Module I/O Typical Current Amps_ ___________________________________________________

Module Board Board +5 VDC +12 VDC -12 VDC_ _____________________________________________________________________________ ____________________________________________________________________________AI-E1 CMA5 CMC8 9.5 0 0_ ____________________________________________________________________________AI-E3 CMA11B CMC13 8.5 0 0_ ____________________________________________________________________________AI-T1 CMA5 CMC5 or CMC5B 9.5 0 0_ ____________________________________________________________________________AI-T3 CMA11B CMC6 8.5 0 0_ ____________________________________________________________________________AI-T3P CMA17 CMC6B (egress) 9.5 0 0

CMC14 (ingress)_ ____________________________________________________________________________CPM-HS TN1009 AWJ2 3.6 0.0 0.0_ ____________________________________________________________________________DKAP MC2P023A1 None 5.7 0.0 0.0_ ____________________________________________________________________________E2A TN1012 ED5P074-30,G1 4.3 0.0 0.0_ ____________________________________________________________________________FRM MC1D143A1 AWJ24 4.3 0.035 0.135

CSD1 5.5 0.0 0.0

CSD2 5.5 0.0 0.0

CSD3 5.5 0.0 0.0_ ____________________________________________________________________________FRM-M2 CTG1 CMC20 7.0 0.0 0.0

CMC18 7.0 0.0 0.0

CMC19 7.0 0.0 0.0_ ____________________________________________________________________________GAR CMA15 CMC14 8.5 0 0_ ____________________________________________________________________________LPM TN2229 CSD6 2.5 0 0_ ____________________________________________________________________________MSM TN2111B AWJ4 4.5 0.120 0.120_ ____________________________________________________________________________

_


Interface Modules________________TABLE 5-52. Interface Module and I/O Board Electrical Service Requirements(continued)_ ____________________________________________________________________________

Module I/O Typical Current Amps_ ________________________________________________Module Board Board +5 VDC +12 VDC -12 VDC_ _____________________________________________________________________________ ____________________________________________________________________________SLM UN221 ED5P077-30,G1 7.0 0.085 0.125

_ _________________________________________________________________

MC5P025A1 ED5P080-30,G1 7.0 0.085 0.125_ ____________________________________________________________________________SYNC8 MC1D089A1 AWJ5 5.8 0.075 0.085

(bsc3270) AWJ6 5.8 0.075 0.085

AWJ17 5.8 0.165 0.165

AWJ18 5.8 0.165 0.165_ ____________________________________________________________________________TSM8 MC1D088A1 AWJ5 5.8 0.075 0.085

AWJ6 5.8 0.075 0.085

AWJ7 5.8 0.165 0.165

AWJ8 5.8 0.165 0.165

AWJ17 5.8 0.165 0.165

AWJ18 5.8 0.165 0.165_ ____________________________________________________________________________TSM-T1 MC1D149A1 AWJ24 4.3 0.035 0.135_ ____________________________________________________________________________TY6 TN1006 ED5P066-30,G1 4.3 0.075 0.096_ ____________________________________________________________________________TY12 TN2157/TN1011C AWJ4 3.4 0.075 0.065_ ____________________________________________________________________________X.25 TN2094 AWJ5 5.7 0.075 0.085

AWJ6 5.7 0.075 0.085

AWJ17 5.7 0.165 0.165

AWJ18 5.7 0.165 0.165_ ____________________________________________________________________________X.25P MC1D153A1 AWJ24 4.3 0.035 0.135

CSD4 5.3 0 0_ ____________________________________________________________________________X.75 MC1D151A1 AWJ24 4.3 0.035 0.135_ ____________________________________________________________________________


________________Connection-Oriented Network

Services

Fundamentals 6-3Physical and Logical Associations 6-3Establishing a Connection 6-4

Address Planning 6-5

Routing Strategies 6-6Assigning Node Addresses 6-6Assigning Trunk Groups 6-8

Endpoint Routing Plan 6-9Assigning Local Groups 6-9Assigning Group Security 6-10Assigning Endpoint Addresses 6-10


________________Connection-Oriented Network

Services

The ability to establish a connection from one node endpoint to another node endpoint anywherewithin a network is a fundamental service that Data Networking Products nodes provide. Thisfundamental service is called connection-oriented network service (CONS). Its rich set ofcapabilities include address plans, group associations, routing strategies, and security methods.These capabilities must be planned and administered in the database in a seamless manner inorder to provide reliable network service to all end users.

This chapter should be used as starting point when planning a connection-oriented network. Itdescribes address, routing, and security plans for a CONS environment. It includes an overviewof all concepts presented and a simple example to help explain those concepts.

Other aspects of planning a network in a CONS environment that are treated elsewhere are asfollows:

A brief explanation of all considerations involved when planning a network is provided in theOverview chapter.

Detailed hardware information relating to the connection points discussed later in this chapteris provided in the Node, Concentrators and Multiplexers, Trunks, and Interface Moduleschapters.

Detailed planning information about addressing, groups, routing, and security is provided inthe Addresses and Groups, Routing, and Security chapters.

An overview of the configuration database is provided in the Database chapter.

Fundamentals

Each physical unit that must be connected to a network is a connection point. A connectionconsists of establishing a path from the physical unit to the network to another physical unit usinga logical or physical address. Planning a CONS environment is therefore concerned withdetermining the required associations of logical addresses to physical units, and then assigningnames and properties to these associations.

Physical and Logical Associations

The physical units that are likely to become connection points in a network include the following:

A customer endpoint is a specific customer-end device located on the originating orterminating end of a connection within the network. This device can be a PC, a hostcomputer, a modem or a pool of modems, a printer, or a router or bridging device.


Connection-Oriented Network Services________________An interface connection point is the specific physical and logical connection point for thecustomer endpoint into the network. Depending on the type of service for which the modulecomponent is administered, this point could be a module, port, or channel.

For the simplest asynchronous connection, a customer endpoint (a PC) is connected to aspecific module (a TY12) and physical port on that module (port 1). Remember that aninterface connection point can be made on a node or on a concentrator or multiplexer that isconnected to a node.

A trunk connection point is a specific physical connection for trunk facilities to other nodes inthe network. This point is typically a particular trunk module and port.

Nodes are the points in the network where connections are made from interface connectionpoints to other interface connection points or to trunk connection points to another node.

Sets of logical entities must also be determined to establish connections. These include thefollowing:

Local groups are groupings of one or more related customer endpoints. A connection can bemade to a single, specific customer endpoint or to any one of a collection of endpoints; forexample, any modem in a pool of modems.

Trunk groups are groupings of one or more trunk modules and/or ports that can be used toreach another part of the network.

A network address is a logical name used to identify the connection endpoint that should beestablished.

A connection is made by using this logical name, called a network address, and associating it withthese logical entities and physical units.

Establishing a Connection

Connection service planning involves the following steps:

1. Determine the addressing plan that best meets the needs of the network.

2. Establish network addresses that are to be associated with each node or sets of nodes in thenetwork.

3. Determine the overall routing plan based on the network topology and addresses associatedwith each node.

4. Group the trunk connection points based on the routing paths that must be established in thenetwork. Give each trunk group a logical name.

Trunk ----> Trunk

Group Connection

Point


Connection-Oriented Network Services________________5. Group customer endpoints based on access, service, and security requirements. Give each

local group a logical name.

Local ----> Interface ----> Customer

Group Connection Endpoint

Point

6. Establish a network address for the local groups based on the connection servicerequirements.

Network ----> Local ----> Interface ----> Customer

Address Group Connection Endpoint

Point

Address Planning

Data Networking Products nodes support a network addressing plan in which any destination canbe an alphanumeric mnemonic name, a numeric address, or both. The addressing scheme ishierarchical; each address can contain four levels in either or both of the following formats.

Mnemonic address format:

network/area/exchange/station.<optional parameters>

For example: usa/nj/central/host1

Numeric address format:

DNIC/SR/SA/EPN.<optional parameters>

For example: 1111/222/333/1212

where

The Data Network Identification Code (DNIC) is the fourth or network level of addressing(represented by a 4-digit number) used to route calls to other networks.

The Service Region (SR) is the third or area level of addressing (represented by a 3-digitnumber) used to route calls to an area that contains a group of exchanges.

The Service Area (SA) is the second or exchange level of addressing (represented by a 3-digit number) used to route calls to a group of endpoints that can be on one or more nodes.

The Endpoint Number (EPN) is the first or lowest level of addressing (represented by a 4-digit number) used to route calls to a local station within the same exchange. Each stationcan be assigned one or a range of EPNs.

For example: 1234/908/555/6789 is a valid numeric address.


Connection-Oriented Network Services________________The minimum required address level is a local name or EPN. Each higher level can be added tofurther define the address. The mnemonic and numeric parts of the address can be mixed.

The planner must determine what type of addressing plan should be used and how manyaddressing levels are needed. Factors that affect these determinations include the network size,the ease or difficulty in which address assignments can be made, user preferences, and servicesneeded on the network. For example, the numeric numbering plan might be selected if X.25interfaces are used because the numeric North American Numbering Plan is the default.

Routing Strategies

The network routing plan involves assigning addresses to nodes and establishing the associationof these addresses to trunk groups and the physical trunk modules.

Assigning Node Addresses

Before node addresses can be assigned, the planner must determine how addresses are to beassociated with the nodes in the network and the type of routing plan that is to be used.

Two types of routing plans are possible:

With hierarchical default routing, the network is structured hierarchically with each topaddressing level consisting of one hub node and many leaf nodes. Each node needs a minimalamount of routing information consisting of what group of addresses are on the directlyconnected nodes only.

With full (non-default) routing, network topology is not constrained. Each node needs routinginformation to determine which of the directly connected nodes is used to reach any address.

Some mixture of these plans is also possible.

Once a routing plan is determined, the mnemonic or numeric representation for each level can bemade. Each address level is assigned to one or more nodes in the network. Typically the toplevel describes the network from an external viewpoint, for example, the country or companyname. Each other level represents a geographical region because each is associated with a groupof physical nodes.

The following figure shows a sample network that will be used to explain the planning functionfor connection services. It is a simple network that consists of four customer endpoints (EndpointW, X, Y, and Z ) that are connected to two nodes (Node A and Node B). The associated modulesand ports are also labeled, as well as the trunk modules and ports that interconnect the nodesthrough a third node, Node C.


Connection-Oriented Network Services________________

Endpoint W

Endpoint X

123

164

26

35

Node A

1

1

17

18

19

20

Node C

21 22

Endpoint Y

Endpoint Z

182

198

56

23

Node B

1

1

TrunkGroup

1

1

1

1

TrunkGroup

Trunks to Other Nodes

FIGURE 6-1. Connection Services Sample Network

Using the network in Figure 6-1, the following assignments could be made:

All Nodes:

Network level: usaThe network is associated with the USA (usa).

All Nodes:

Area level: njNode C is the hub node to reach all exchanges in NJ (nj). Other areas might exist inother states and are reached through Node C.

Node A:

Exchange level: monmouth and oceanNode A contains two different exchanges consisting of all endpoints in Monmouth(monmouth) and Ocean (ocean) counties.


Connection-Oriented Network Services________________Node B:

Exchange level: middlesexNode A contains all endpoints in Middlesex (middlesex) county.

(Other addressing assignments are possible including splitting an exchange across multiplenodes.)

The hierarchical nature of the addressing plans puts constraints on assigning addresses to nodes.In particular, assigning addresses to nodes must be such that it is possible to predict the one paththat will be taken to reach any other address. Special care must be taken when using the fullrouting plan to avoid routing loops.

Assigning Trunk Groups

Once addresses are assigned to nodes, routing can be established using the physical trunk betweenthe nodes.

A trunk group is created consisting of the physical trunks that are used to route traffic to anaddress. Each trunk group created is given a logical name. Associated with each trunk group arethe addresses that can be reached using that trunk group.

With default routing, each trunk group consists of a set of physical trunks that are connected toone other node. More elaborate trunk groups can be created to achieve alternate routing paths(each trunk group consisting of the physical trunks to multiple nodes), but loops must be avoided.Optionally, security patterns can also be associated with each trunk group.

Using the network in Figure 6-1, the following assignments could be made:

Node C:

Trunk group: trkCA

— Consists of the two trunks going from Node C to Node A, which are the trunkson Node C, Module 17, Port 1 and Node C, Module 18, Port 1.

— Addresses to network usa, area nj, and exchange monmouth or ocean are reachedvia this trunk group.

Trunk group: trkCB

— Consists of the two trunks going from Node C to Node B, which are the trunks onNode C, Module 19, Port 1 and Node C, Module 20, Port 1.

— Addresses to network usa, area nj, and exchange middlesex are reached via thistrunk group.


Connection-Oriented Network Services________________Trunk group: trkCx

— Consists of the two trunks going from Node C to Node X (not shown), which arethe trunks on Node C, Module 21, Port 1 and Node C, Module 22, Port 1.

— Addresses to network usa, area not equal to nj (that is, all areas outside of NewJersey), are reached via this trunk group.

Node A:

Trunk group: trkAC

— Consists of the two trunks going from Node A to Node C, which are the trunkson Node A, Module 26, Port 1 and Node A, Module 35, Port 1.

— Addresses to network usa, area nj, and exchange not equal to monmouth and notequal to ocean are reached via this trunk group.

Node B:

Trunk group: trkBC

— Consists of the two trunks going from Node B to Node C, which are the trunks onNode B, Module 56, Port 1 and Node B, Module 23, Port 1.

— Addresses to network usa, area nj, and exchange not equal to middlesex arereached via this trunk group.

Endpoint Routing Plan

To make connections to customer endpoints, customer endpoints must be associated with localgroups which define the properties of each connection. This section describes the fundamentalsof this final assignment step in CONS planning.

Assigning Local Groups

Customer endpoints must be associated with a local group to allow connections to proceed. Thelocal group describes the connection properties of a set of endpoints including the type ofconnections allowed and security information. Each local group is given a logical name. Thesegroups are possible:


Connection-Oriented Network Services________________Endpoints in an originating group can only originate calls. Since these endpoints do notreceive calls, an endpoint address is not assigned to an originating group. The originatinggroup is used to define security information and to group similar type endpoints.

Endpoints in a receiving group can only receive calls. An endpoint address is associated witheach receiving group, as well as security information and other connection parameters such asthe method to choose which endpoint in the group is to receive the next call.

Endpoints in a two-way group can both originate and receive calls. An endpoint address isassociated with each two-way group, as well as security information and other connectionparameters.

For the many Data Networking Products services, it is wise to associate several like endpointswith one group; for example, many ports providing the same service, such as modem pools,should be grouped together.

Assigning Group Security

Several types of security are supported by Data Networking Products nodes. Associated witheach group (trunk and/or local) is a security pattern that limits possible connections. In general,security is achieved by matching the originating address to a security pattern. For example,security patterns can be associated with trunks to block calls from traversing the trunk; they canbe associated with endpoint groups to block calls from endpoints not in a specified group.

Assigning Endpoint Addresses

For each receiving or two-way group, an address must be assigned that is consistent with theaddresses assigned to the node. Each receiving or two-way group can be assigned a singleendpoint address or an address consisting of a range of EPNs depending on the need. The choiceof address is only limited by the addressing plan chosen for the network. Remember that the fulladdress must be unique to the network.

Returning to the example network in Figure 6-1, assume that Endpoint W only originates calls;Endpoint X originates calls and can only receive calls from Endpoint W; and Endpoints Y and Z,which can be used by any endpoint in the NJ (nj) area, provide the receive-only service.


Connection-Oriented Network Services________________Node A:

Local group: orig1This group is used for all originate-only endpoints on Node A.

Local group: endXSecurity pattern: orig1This group defines the connection properties of Endpoint X.

Endpoint W:Local group: orig1Address: not necessary

Endpoint X:Local group: endXExchange: oceanEPN: 1234The full address for this endpoint is usa/nj/ocean/1234. It can originate calls, but canonly receive calls from group orig1.

Node B:

Local group: serviceYZSecurity pattern: usa/nj/*/*Routing is round robin.This group is used to access the service provided by Endpoints Y and Z. Endpoints inthis group are selected using a round robin algorithm. It can only receive calls from areausa/nj.

Endpoint Y:Local group: serviceYZEPN: printThe full address for this endpoint is usa/nj/middlesex/print. It can only receive callsfrom area usa/nj.

Endpoint Z:Local group: serviceYZEPN: printThe full address for this endpoint is usa/nj/middlesex/print. It can only receive callsfrom area usa/nj.


________________Addresses and Groups

Service Addresses 7-3Address Types 7-4Address Formats 7-4Address Levels 7-7Naming Mnemonic Addresses 7-8Special Addresses 7-9End User Addressing 7-10Directory Assistance 7-11International Addresses 7-12

Physical Addresses 7-14

Combination Addresses 7-15

Groups 7-16Originating Groups 7-17Receiving Groups 7-17Two-way Groups 7-18Special Groups 7-18Trunk Groups 7-18Administration of Groups 7-19


________________Addresses and Groups

Addresses are strings of alphanumeric characters or numbers that the network administrator usesin a connection-oriented network service (CONS) environment to define the location of a logicaldevice residing in a network. The three forms of addresses used in the network are the following:

A service address is used by end users to communicate with network destinations. A serviceaddress can be one of two types and each contains various levels that define the network, area,exchange, and local service to which the logical device belongs.

A physical address identifies a network component by its physical location within a node.

A combination address is formed when a service address and a physical address are mixed soa specific destination module channel/port can be called in a service group.

Groups are used to associate addresses with physical interfaces on the node. There are two typesof groups: local groups and trunk groups.

This chapter provides all details on addresses and groups. Other aspects about addresses andgroups treated elsewhere are as follows:

An overview of how addressing relates to physical units (the hardware), local and trunkgroups, and routing is provided in the Connection-Oriented Network Services chapter.Procedures for administering addresses and groups are provided in the Node Reference.

The relationship to network security is explained in the Security chapter.

The relationship to call routing is explained in the Routing chapter.

The relationship to other database elements is explained in the Database chapter.

Service Addresses

The network administrator assigns service addresses to call destinations. Each destination on thenode that can be called must have at least one associated service address. Service addresses areof two types: mnemonic or numeric. The network node uses the format of a mnemonic ornumeric address and the level of the address supplied to identify and properly route the call.


Addresses and Groups________________Address Types

Mnemonic addresses, which are alphanumeric strings, are often used to identify endpoints withina network. In addition, mnemonic addresses are used to designate special addresses forspeedcalls, aliases, directory assistance, and billing.

Numeric addresses, which are strings of numbers, conform to three standard numbering plans fornational and international call addressing and routing:

X.121 International Numbering Plan defines the numeric address format for public voice anddata networks outside of North America. The X.121 International Numbering Plan, whichadheres to the 1988 CCITT Recommendation for X.121, is used to address packet-switchedpublic data networks (PSPDNs) connected through X.75 modules and X.25 PDN ports withsome restrictions.

X.121 North American Numbering Plan (NANP) is used in the public voice and data networkswithin North America. The numeric addresses devised from this numbering plan conform tothe standard designated for network terminal numbers (NTNs), which provide support forinterworking with X.25 services.

The X.121 NANP is a particular case of the X.121 International Numbering Plan.

E.164 Numbering Plan, which is a format provided by the X.121 International Numbering Plan,is used by the Integrated Services Digital Network (ISDN) and the connectionless networkservice (CLNS) used in a BNS-2000 SMDS network.

A given endpoint can be associated with a mnemonic address, a numeric address, or both. Ingeneral, numeric addresses are assigned to network destinations (endpoints) that connect to 5ESSswitch endpoints, PDN endpoints, PSPDN endpoints, or X.25 hosts; but numeric addresses canalso be assigned to endpoints that originate calls. When a numeric address to is assigned to anendpoint that originates calls, the originating endpoint address is passed to the call destination;therefore it must adhere to a format that the addressing logic of the destination endpoint canrecognize. If the originating endpoint does not have an assigned numeric address, the numericaddress of the gateway assigned to the switch or PDN is used.

Address Formats

Mnemonic and numeric address have different formats. The following table shows the addresstype and its format. The address length is also included beneath the address format.


Addresses and Groups________________TABLE 7-1. Address Types and Formats

_ ________________________________________________________________________Address Type Numbering Plan Address Format_ _________________________________________________________________________ ________________________________________________________________________

network/area/exchange/local

Mnemonic N/A_ ________________________________________

(1-8)/(1-8)/(1-8)/(1-8)_ ________________________________________________________________________p DNIC + NTN DCC + NN

Numeric X.121 International_ ____________________

or_ ________________

1 4 + <4-10>

3 + 1_ ________________________________________________________________________p DNIC/SR/SA/EPN

Numeric X.121 North American_ ________________________________________

1 4/3/3/4_ ________________________________________________________________________p <e> CC + N(S)N <e> TCC + N(S)N

Numeric E.164_ ____________________

or_ ________________

1 <1> <1-3> + <4-14> <1> <1-3> + <4-14>_ ________________________________________________________________________

network A network is a string of 1 to 8 alphanumeric characters that names a set of areas that constitute a datanetwork. A network identifies trunks going to other nodes or gateways to other nodes.

The network administrator can associate each node with a network-level address, and can alsoadminister network-level addresses for other networks with which local node devices interact.

area An area is a string of 1 to 8 alphanumeric characters that consists of a set of exchanges that constitute adata area. An area identifies trunks going to other nodes or gateways to other nodes.

The network administrator can associate each node with an area-level address, and can also administerarea-level addresses for other areas in the node’s network with which local node devices interact.

exchange An exchange is a string of 1 to 8 alphanumeric characters that consists of a set of local addresses(devices); it identifies trunks going to other nodes or gateways to other nodes.

The network administrator can associate each node with an exchange-level address, and can alsoadminister exchange-level addresses for other exchanges in the node’s area with which local nodedevices interact.

local A local address is a string of 1 to 8 alphanumeric characters that names a local device (endpoint) on alocal node or on another node(s) in the same exchange.

If the device is on the same node, the local address identifies a device on the node. If the device is onanother node, the local address identifies a trunk to the other node.

p A prefix is an optional 1-digit number from 0 to 9. Depending on call origin, call destination, andaddress format, a prefix can be a local node prefix or an international prefix.

The network uses the local node prefix when matching the first digit of incoming calls originating fromendpoints having an X.121 international or E.164 address. If the prefix is equal to the local node prefix,the address is treated as an X.121 international address. If the prefix is not equal to the local nodeprefix, the address is treated as an X.121 NANP. The local node prefix is administered with the nodecommand. The network uses the international prefix to identify a subscriber’s node in another country.The international prefix is administered with the node command.

DNIC A Data Network Identification Code is a 4-digit number that identifies a data network. A DNIC can


Addresses and Groups________________consist of the following:

• Data Country Code (DCC) is a 3-digit number from 000 to 999, which can be the first 3 digits of theDNIC.

• National Number (NN) is a 1-digit number from 0 to 9, which can be used as the last digit of theDNIC.

A Public Data Network Identifier (PDNID) is analogous to a NN. It is a 1-digit number from 0 to 9,which can be the last digit of the DNIC.

NTN A Network Terminal Number is a 4 to 10-digit number. An NTN can consist of a

• Service Region (SR) is a 3-digit number from 000 to 999 specifying a group of areas.

• Service Area (SA) is a 3-digit number from 000 to 999 specifying a group of exchanges.

• Endpoint number (EPN) is a 4-digit number from 0000 to 9999 specifying a local device.

e An escape code is a 1-digit number from the set of 0, 8, or 9 which indicates that the subscriber addressthat follows must be bypassed (escaped) because it is not supported by the X.121 numbering plan. Thesupported escape codes and the numbering plans that they represent are the following:

Escape Code Numbering Plan Being Bypassed

0 E.164 Numbering Plan

Calls from PSPDN to ISDN/PSTN or

E.163 Recommendation (a subset of E.164)

8 F.69 Numbering Plan; Telex Numbering Plan

9 E.164 Numbering Plan; calls from PSPDN to ISDN

Escape codes and their modifiers are administered through the enter sphaddr command.

CC/TCC A Country Code is a 1 to 3-digit number ranging from 1 to 999 that specifies the destinationcountry or geographical location. (The CC of the United States is 1.) The CC is administered withthe node command.

A Telephone Country Code (TCC), which is analogous to the CC, is a 1 to 3-digit number rangingfrom 1 to 999 that specifies the destination country or geographical location.

N(S)N A National (Significant) Number is a 4 to 10-digit number that specifies the destinationsubscriber. An N(S)N can consist of a:

• National destination code (NDC) specifies the address of the destination network that serves thedestination subscriber. Depending on the length of the CC, the NDC can be one of thefollowing lengths:

If the CC is 1 digit, the NDC can be 5 to 14 digits.If the CC is 2 digits, the NDC can be 4 to 13 digits.If the CC is 3 digits, the NDC can be 4 to 12 digits.

• Subscriber Number (SN) is a 10-digit number from 0 to 9. An SN, which is analogous to anEPN, specifies the subscriber address in the same local network or numbering area.

The NDC, when combined with the SN, constitutes the N(S)N of the international ISDN number.


Addresses and Groups________________Address Levels

Although their address formats differ, both mnemonic and numeric addresses identify the fourlevels in a network hierarchy:

network, which is one or more areas

area, which is one or more exchanges

exchange, which is one or more nodes

local, which is the destination endpoint

On each node, local addresses identify the endpoints in the exchange. Exchange, area, andnetwork addresses always identify trunks to other nodes or gateways.

NOTE: Because the format of the mnemonic address was expanded in Datakit II VCS Release2.0, a network that includes Datakit II VCS Release 1.0 and Datakit VCS nodes shouldbe administered so calls to those nodes do not use four-level addresses.

The node must define an address for every destination (endpoint) to which a device on the node isto have access. If devices have access only to destinations on the same node, only local-leveladdresses might be necessary. If destinations are in other exchanges, areas, or networks,exchange-, area- and network-level addresses, as appropriate, must be administered; it is notnecessary to administer the complete destination address, because routing is based on the highestpart of the address. The following table correlates the address levels to the appropriate mnemonicor numeric term.

TABLE 7-2. Comparison of Mnemonic and X.121 Numeric Address Levels

_ _____________________________________________________________________________Mnemonic Numeric

LevelAddress Address

Comments_ ______________________________________________________________________________ _____________________________________________________________________________

nodeprefix

Local NodePrefix

Can be the local node prefix or international prefixdepending on the call.

not used

_ _____________________________________________________________________________LocalNetwork

Local DNICor CC+N(S)Nor TCC+N(S)N

The highest level of addressing; can be a mnemonic ornumeric address, or both.

network

_ _____________________________________________________________________________


Addresses and Groups________________TABLE 7-2. Comparison of Mnemonic and X.121 Numeric Address Levels(continued)_ _____________________________________________________________________________

Mnemonic NumericLevel

Address AddressComments

_ ______________________________________________________________________________ _____________________________________________________________________________Local Area Local X.121

Service Region(SR)

Can be a mnemonic or a numeric address, or both. area

_ _____________________________________________________________________________Local X.121Service Area (SA)

Can be a mnemonic or a numeric address, or both. exchange Exchange

_ _____________________________________________________________________________EPN or range ofEPNs

Can be a mnemonic, a numeric (an EPN or range of EPNs),or both.

local Local

_ _____________________________________________________________________________

Naming Mnemonic Addresses

The network administrator can choose mnemonic addresses, within the constraints listed below.It makes sense to pick addresses significant to end users. If end users know a service by aparticular name, for example sales or accounting, use that name or a generally familiarabbreviation. In addition, consult with host administrators on the node and with administrators ofsimilar type remote nodes and other types of nodes to coordinate the addressing scheme.

When planning the addresses for networks, areas, exchanges, and local services, and forspeedcalls and aliases, keep the following rules in mind:

Each service address within a level—that is, network, area, exchange, local (includingspeedcalls and aliases)—must be unique.

A mnemonic service address can be alphabetic, numeric, or alphanumeric. It cannot,however, have the same format as a numeric address at the same level.

A mnemonic service address can be as long as eight characters.

Certain characters cannot be used in service addresses. The following characters are reservedfor special service addresses or editing and other functions:

_ _______________________________________________________/ *slash (or virgule) asterisk_ _______________________________________________________. =dot (or period) equals sign_ _______________________________________________________# [ ]number (or pound) sign square brackets_ _______________________________________________________@ !at exclamation mark_ _______________________________________________________Backspacebackspace

_ _______________________________________________________


Addresses and Groups________________Special Addresses

Data Networking Products nodes use several types of special mnemonic addresses that can bedefined when information is entered in the database. These include standard mnemonic addressesdesigned as part of the software, such as the ? entered to obtain directory assistance, shorteraddress forms (speedcalls and aliases) that can be administered to make communication quickerand easier for end users, and special formats for billing and default routing.

Speedcalls

A speedcall is a short mnemonic address that stands for a longer local or multilevel address.Speedcalls make setting up calls easier for users who make frequent calls to a device in a differentexchange or area.

Although a speedcall address can be created at any level, the administrator usually creates one-level addresses and associates them with a two-, three-, or four-level address. When the shorteraddress is entered by a user as a destination code, the system expands it into the longer address.

For example, a user can enter the speedcall address go as a call address, and the system translatesit into the dial string that the network administrator defined for it with enter address.

Depending on what the network administrator specified, it might represent the one-level addressgopher, the two-level address bldg1/gopher, the three-level address ny/bldg1/gopher, or the four-level address usa/ny/bldg1/gopher.

Aliases

Aliases are different mnemonic addresses for the same area address or exchange address. In anexchange with three nodes, for example, you may want to address each node to collect its billingdata; you will need an exchange-level alias for each node do this. Or you may want a user toaccess a service on a given node when more than one node provides the same service. Aliasexchange addresses might also be used when there is private trunking on a shared node. The aliasmust be designated as a network-, area-, or exchange-level address, whichever is appropriate, nota local service address. Then the alias address is tied to the special group ?lcl, described underSpecial Groups.

For example, consider a large multinode network in which four nodes share an exchange. Allhosts connected to any of the four nodes have local service addresses, defined in the database ateach node.

As PCs are added to the network, database limits on service addresses can be quickly exceeded ifeach one has a service address that is defined at each node. Use the following method to defineaddresses for PCs on other nodes in the same exchange without exhausting system resources.

Assign each node in the exchange a unique alias exchange address, such as nodeA, nodeB,nodeC, and nodeD.

Define the PCs connected to each of the nodes only in the database of the node to which theyare connected.


Addresses and Groups________________Define other receiving devices, such as hosts, in all node databases.

Define the alias exchange addresses of each node in each node database.

An alias exchange address must be defined in the database of every node within the local area,so each node can route a call using the alias exchange address. Outside the local area, thealias exchange (just like any exchange) need not be known to other nodes. It must, however,be part of the destination dial string.

For users on nodeA to access a PC on nodeB, they must enter a call address in the format<nodeB/service_address>.

To access any host on any node from any of the four nodes only the local service address needbe entered.

End User Addressing

To gain access to a network destination within North America, an end user can type in, at theterminal keyboard, the four address levels, separated by slashes. These addresses areinterchangeable at any level. For example:

_ ______________________________Format Address_ _______________________________ ______________________________

mnemonic network/area/exchange/local_ ______________________________numeric DNIC/SR/SA/EPN_ ______________________________numeric CC+N(S)N/SR/SA/EPN_ ______________________________numeric TCC+N(S)N/SR/SA/EPN_ ______________________________mixed network/SR/SA/local_ ______________________________mixed DNIC/area/exchange/EPN_ ______________________________

Depending on the particular destination, the end user only has to input certain address levels. Forendpoints within North America, the full four-part destination address of:

network (DNIC)/area (SR)/exchange (SA)/local (EPN)

works for all cases.


Addresses and Groups________________Usually, the end user only has to enter one or two address levels. For example:

_____________________________________________________________Destination Address Levels

Location Address Format Required__________________________________________________________________________________________________________________________same exchange (SA) home mnemonic

as originating device 1234 numeric local EPN_____________________________________________________________different exchange (SA); mt/home mnemonic

same area (SR) 321/1234 numeric exchange (SA) and

as originating device 321/home mixed local (EPN)_____________________________________________________________different area (SR); nj/mt/home mnemonic

same network 201/321/1234 numeric

as originating device 201/mt/1234 mixed three part address_____________________________________________________________different network (DNIC) na/nj/mt/home mnemonic

from originating device 4321/201/321/1234 numeric

4321/nj/321/home mixed four part address_____________________________________________________________

For endpoints outside of North America, see International Addresses in this chapter.

Directory Assistance

The directory assistance feature enables end users to secure an on-line list of service addresses towhich the end user has been given access. The mnemonic address for directory assistance is thequestion mark symbol: ?. If this address is administered, an end user can request information onaccessible destination addresses. The administrator controls the information an end user sees onthe screen. The end user makes a request by entering the address for directory assistance at thenetwork DESTINATION: prompt. For directory assistance in another node, the ? address mustbe administered in that node.

The address format is as follows:

For addresses in the same exchange (SA): ?

For addresses in another exchange (SA) but the same area (SR): <exchange (SA)>/?

For addresses in another area (SR): <area (SR)>/<exchange (SA)>/?

For addresses in another network (DNIC):<network (DNIC)/<area (SR)>/<exchange (SA)>/<station (EPN)>/?

If directory entries are made, an end user can enter ? at the destination prompt and see the entriesfor service addresses to which the user’s originating group has been granted access. If you choosenot to create a directory entry, neither an entry nor the address will appear in a directoryassistance screen.

When designing your database for directory assistance, consider security needs. It may not bedesirable to have end users print out lists of network destinations.


Addresses and Groups________________Directory assistance is, however, a helpful feature in multinodal networks, especially those withmultiple hosts and PCs. When defining directory assistance for such networks, give specialconsideration to entries for PCs defined as two-way. When too many two-way ports have uniquegroups and service addresses, the list of addresses can be extensive. Cut down on this list byfollowing a naming convention. For example, if each PC is given a service address pcxxxx, wherexxxx is the end user’s extension, a single directory entry could suffice for all users.

International Addresses

The X.121 International Numbering Plan defines an address format that is not as rigid as theX.121 NANP format, where routing is always performed on only 4, 7, or 10 digits. Calls withX.121 international addresses are routed on the digits in positions from 0 to 9 in the address, zerobeing the most significant. The last digits are analyzed only to reach the destination endpoint.Not all digits are used for routing: whenever a subset of digits (including at least the DNIC) ispresent, the subset is used for routing, regardless of how many digits are present.

With E.164 addresses, calls are routed on the 7 most-significant digits in the address. Theremainder of the address identifies the endpoint inside a national network. In addition,administerable escape codes enable an E.164 address to be identified as a national call on anational network and to be bypassed.

For call routing, these address formats are interpreted, translated, and routed as follows:

If the first digit (prefix) matches the node prefix, the address is an X.121 international address.

If the first digit (prefix) does not match the node prefix, the address is an X.121 NANPaddress.

If the address is an X.121 international address, that is, if the first digit (the prefix) matchesthe node prefix, the second digit is examined. If the second digit matches an administeredescape code, the address is an E.164 address. (Escape codes are administered with entersphaddr.)

The call is routed on up to 6 digits of the CC+N(S)N or TCC+N(S)N. Because the first 7digits of the CC + N(S)N are analyzed and the length of the CC varies, only a part of theN(S)N is used to route the call:

If the CC (TCC) is 3 digits, only the first 4 digits of N(SN) are analyzed.

If the CC (TCC) is 2 digits, only the first 5 digits of N(SN) are analyzed.

If the CC (TCC) is 1 digit, only the first 6 digits of N(SN) are analyzed.


Addresses and Groups________________NOTE: An X.121 international address supports a private network identification code

(PNIC). A PNIC, which consists of up to 6 digits, is assigned to each private datanetwork contained within a group of private data networks identified by a specificDNIC.

An X.121 international addresses is routed on 4 to 10 digits of the DNIC+NTN.

An E.164 address is routed on 1 to 7 digits of the CC/TCC+N(S)N.

If the address consists of a prefix plus 4 digits, the 4 digits are a node EPN.

The following table shows the address formats for calls that originate and terminate on a DataNetworking Products network.

TABLE 7-3. Call Routing Scenarios

_ ___________________________________________________________________Data

Networking National Call International Call International CallProduct through through through

User National Gateway National Gateway International Gateway_ ____________________________________________________________________ ___________________________________________________________________p+DNIC+NTN u+NTN i+DNIC+NTN DNIC+NTN_ ____________________________________________________________________ ___________________________________________________________________p+e+CC+N(S)N m+N(S)N i+e+CC+N(S)N e+CC+N(S)N_ ___________________________________________________________________

_______________________________________Where:_______________________________________

International Prefix i

Modifier for Escape Code (e); can include TCC ifTCC suppression is not required

m

DNIC if DCC stripping is not required or lastdigit of DNIC if DCC is stripped

u

_______________________________________

Scenario 1: A call originates on a Data Networking Products network EPN with theformat p+DNIC+NTN. The prefix is always suppressed if the call is destined for an X.75national gateway. The DCC might be stripped if such an option is configured at the X.75gateway. In this case, the prefix is optional and is not the same as the node prefix. TheX.25 network receives DNIC followed by NTN or the last digit of DNIC followed byNTN.

Scenario 2: A call originates on a Data Networking Products network EPN with theformats p+9+TCC+N(S)N and p+0+CC+N(S)N. The escape code and CC/TCC arereplaced by an optional modifier, which precedes the N(S)N (m+N(S)N). The CC/TCCmight be suppressed, depending on whether the CC/TCC is defined in the modifier.


Addresses and Groups________________For calls received from an X.75 gateway, depending on the format of the address received by thegateway and the type of gateway, the address is modified so it conforms to the X.121International format. Modifications might include adding or changing the prefix, replacing themodifier, or adding a DCC. The call is then routed.

For calls originating from an international X.75 gateway, the node prefix is added to the address.For international calls originating from an X.75 national gateway, the international prefix isreplaced by the node prefix. For calls originating on a Data Networking Products network andgoing through a national X.75 gateway to another national network, only two formats areallowed:

X.121 format, for calls going to another network having X.121 routing capabilities.

The Data Networking Products user would dial an address having the format p+DNIC+NTNand the destination network would receive an address having the format u+NTN.

E.164 format, for calls going to another network having E.164 routing capabilities.

The Data Networking Products user would dial an address having the format p+e+CC+N(S)Nand the destination network would receive an address having the format m+N(S)N.

For calls originating from an X.25 PDN to a Data Networking Products endpoint, addressmapping is permitted. (Address maps can be optionally configured.) The gateway address map isused to map the last 4 digits of the X.25 called address to the address of an appropriate DataNetworking Products endpoint. If the last 4 digits of the X.25 called address are not in thegateway address map, the call is cleared when no entries are in the gateway mapping table.

Physical Addresses

The network administrator must enter physical address identifiers into the database for each majorsystem component through which data is routed. These physical addresses correspond to nodeand concentrator slot numbers and to module ports and channels. They appear on reports andalarm messages, but are not ordinarily used as service addresses. A combination of a serviceaddress and a physical address, however, can sometimes be used by a network administrator at anasynchronous terminal for testing purposes; see Combination Addresses. Physical addresses canalso be used to specify a PDD to support PVCs for frame relay traffic, X.25/X.25P/X.75 traffic,and bridging services.

Physical addresses have a hierarchical structure from the node slot to concentrator slots to moduleports or channels. When an address includes both a node level and concentrator level, these twolevels are separated by a slash (/). Port and channel numbers are preceded by a dot (.) in somecontexts, and by a space in others.

Components identified with physical addresses are as follows:

Each module in the node is identified by the number of the shelf and logical slot it occupies.


Addresses and Groups________________Each concentrator (including SAMs) is identified by the number of the node slot occupied bythe link interface module (LIM) that connects the concentrator to the node. The address lookslike the address of any other module in the node.

For example, the address of a concentrator connected via a LIM in node slot 27 would be 27.

Each module in a concentrator is identified by a two-level address. The first level is theaddress of the concentrator (see preceding item). The second level is the number of theconcentrator slot occupied by the module. The levels are separated by a slash.

For example, the address of a module in slot 5 of a concentrator connected via a LIM in nodeslot 27 would be 27/5.

Each port and channel on each module is identified by a 1 to 3-digit number, depending on theparticular module. Some modules have physical ports that are numbered, and physicaladdresses are derived from these numbers. The administrator’s ability to address individualports and channels depends on the command (and type of hardware) being used.

The Control Computer adds overhead channels to some module types; in some cases, theseoverhead channels are not addressable, not administrable, or both. Some commands addresschannels within a range, some address to port level, and others can address an individualchannel. Some command entries allow a port address of the form:

<node slot address>/<concentrator slot address>.<port number>.<<virtual port>.<DLCI>>

For example, the full physical address of a port on a module that is residing in a concentratorwould be: 27/14.2; where: 27 is the number of the node slot occupied by a LIM connecting aconcentrator; 14 is the concentrator slot occupied by an interface module; and 2 is the secondport on the interface module. The use of the slash (/) and the point (.) depend on thecommand. If the module is an FRM, the DLCI would then be appended; if the module is anFRM-M2, the virtual port number and the DLCI would then be appended.

Combination Addresses

With a combination of a service address and a physical address, a network administrator or aterminal user at an asynchronous terminal can call a specific destination module channel/port in aservice group. This feature can be used to check if a specific port is operating properly. If themodule resides in a node slot, the address format is the following:

<service address>.<module slot>.<port or channel number>

If the module resides in an MPC, the address format is the following:

<service address>.<concentrator address>/<module slot>.<port or channel number>


Addresses and Groups________________For a SAM connected through a single-link (SAMSL, Trunk-HS, Trunk-T1), the address formatis the following:

<service address>.<SAM module>.<channel>

-or-

<service address>.<SAM module>/<board>.<port>

For example, to determine whether channel 4 on a TY module residing in BNS-2000 node slot 48can support a destination with the address hosta, set up a call as follows:

DESTINATION: hosta.48.4

This addressing format applies only to destination modules; it cannot be used to address a trunkchannel. Slight variations of this address format exist for modules with channel sets, data linkconnection identifiers (DLCIs), or terminal units. Refer to the appropriate module reference forthe correct address format.

Groups

Group names for CONS identify logical sets of module ports or module channels. A group namecan identify a single port, but it more typically identifies a number of ports or channels withcommon uses. The channels going into a host computer, for example, might be associated with asingle group name like acctg. Or a few channels might be associated with the group sales and therest with acctg. Each hardware type has to be in a separate group of similar ports; for example,ports on TY modules have to be in groups that contain only TY ports. Each group can includeonly one or more ports of the same hardware type.

There are two group types: local groups and trunk groups. The devices connected to each nodecan be organized into the following local groups:

originating groups

receiving groups

two-way groups

special groups


Addresses and Groups________________Originating Groups

The main feature of an originating group is that its members can only originate calls; they cannotreceive calls. Therefore, ports or channels connecting to devices that typically originate calls(terminals, dial-in modems) are put into originating groups.

Originating group names provide the basis for security patterns. Groups are usually createdaccording to the host access permissions of the users, as well as location, function, department, orother organizational characteristics. Members of the same group have the same accesspermissions; in other words, they can reach the same destinations. Members share only thesepermissions, however; they do not have to have identical characteristics like baud rate or parity.

It is possible to create one originating group for all originating channels within a node. There areseveral reasons, however, for partitioning the user population into several groups:

Security can be implemented by defining originating groups that may or may not gain accessto a particular service address. Without separate originating groups, there is no way to restrictaccess to specific destination addresses.

Administrative reports can be obtained on a group basis; therefore, it is useful to assign usersto groups that reflect their department, level, or function.

If the node is shared by multiple customers, it is especially important to restrict access bycustomer. Minimally, there would be one group per customer, although several separategroups within customer groups would be a more likely arrangement.

Different types of interface modules on the same node require separate groups.

Receiving Groups

Receiving groups contain channels that can only receive calls and members of a group share thesame service addresses. Ports or channels connecting devices like host computers, dial-outmodems, administration console printers, data switches, and interfaces to other LANs are put intothese groups. Channels assigned to receiving groups cannot originate calls to other destinations.Different types of hardware require different receiving groups, but these different groups can beaccessed through the same service address.

Receiving groups can be assigned round-robin service at the module or port level. Round-robindistributes the traffic load on modules and ports.

At the module level, round-robin will try the modules in the groups in order, starting from whereround-robin left off the last time a call was tried. Example: a group has four modules, a, b, c,and d. The last module to receive a call was c. When a call request is received, the ControlComputer tries to find a port on module d first, and then return to a.

Round-robin at the port level works similarly. If the network administrator does not specifyround-robin service, the default search sequence, first listed, first called, is implemented. Thissequence routes calls to member a first, no matter what module received the last call. If membera is busy, the call is directed to b, and so on. This default is appropriate when the first member isto answer as many calls as possible.


Addresses and Groups________________Two-way Groups

Two-way groups contain channels that can both originate and receive calls. Devices like PCs andhosts are most likely to be connected to channels in two-way groups. FRM ports can only beconfigured as part of two-way groups.

Typically, each two-way PC port is assigned to a unique two-way group. In this way, it can beassociated with a service address (see Addresses in this chapter) and uniquely addressed. Two-way PC ports can be grouped together in a two-way group if it is not necessary to address any onein particular or if EPNs can be used for addressing.

Round-robin service is available.

Special Groups

Typically, special groups are reserved for particular functions and are created automatically by thesystem when a designated command, such as enter node or enter address, in used. Thesegroups, which cannot be deleted, are the following:

?lcl (lcl is for local) is automatically set up when the administrator uses enter node toidentify the node. When the administrator sets up aliases, the alias address (including thenetwork, area, and exchange) must be explicitly associated with the ?lcl group.

?skimiep is associated with the service addresses of nodes that StarKeeper II NMS calls tocollect administration and performance data.

?nmsiep enables the StarKeeper II NMS data communication path for the software downloadfeature that is used in both Datakit II VCS and BNS-2000 systems, and the Inter-CarrierInterface (ICI) feature that is used in BNS-2000 systems.

?smdsbac is used for the connection between the Control Computer and the BilldatsNetwork Server.

?smdsbil is used for call setup between a BNS-2000 AI Module and the Billdats NetworkServer.

Trunk Groups

Trunk groups contain only CONS trunk modules that allow communication with other nodes. Alltrunks in a trunk group should connect to the same node. As with receiving groups and two-waygroups, trunk groups can be administered for round-robin service.


Addresses and Groups________________Administration of Groups

The network administrator enters the group in the database and names the group with oneiteration of enter group.

Originating groups are usually named according to the group location or function; for example,winga, wingb, or acctg.

The names of trunk groups usually suggest where the trunk connection ends; for example, bldg2or newark. Administration of originating group name security patterns, which limit access todestination service addresses, is easier if common prefixes or suffixes are used for similarpurposes. Keep in mind the following rules and considerations when naming groups:

Each group name must be unique to the node; however, a group can have the same name as amnemonic service address.

The group name can be alphabetic, numeric, or alphanumeric.

The group name can be eight characters long.

Certain characters, which are reserved for editing and other functions, cannot be used in groupnames:

_ _______________________________________________________/ *slash (or virgule) asterisk_ _______________________________________________________. =dot (or period) equals sign_ _______________________________________________________# [ ]number (or pound) sign square brackets_ _______________________________________________________@ !at exclamation mark_ _______________________________________________________Backspacebackspace

_ _______________________________________________________

After naming a group, the administrator can then specify network access passwords fororiginating groups and round-robin service for receiving groups.

If a network access password is administered, the administrator can specify, at the PASSWORDREQUIRED DURING prompt, when the password prompting sequence is to be displayed on theend user’s terminal. If network_access is specified, the end user is prompted for the networkaccess password as soon as the terminal is turned on or the network is dialed. If select isspecified, the end user can enter the select command to access a particular originatinggroup. Once the password is entered, the end user assumes the network access permissions forthat originating group. If both is specified, the actions resulting from the network_access andselect options occur.


________________Routing

Routing Plans 8-3Default Routing 8-4Full (Non-Default) Routing 8-8

Trunk Groups 8-9

Alternate Routing 8-11Options 8-13

Interworking 8-17


________________Routing

This chapter provides all physical and software-related details for routing in a connection-orientednetwork service (CONS) environment. The chapter includes information on routing networktopologies, routing plans, trunk group configurations, and alternate routing. Other aspects ofrouting are treated elsewhere as follows:

An overview of how routing relates to physical units (the hardware), local and trunk groups,and addressing is provided in the Connection-Oriented Network Services chapter.

The physical and hardware aspects of nodes are explained in the Node chapter.

The physical and hardware aspects of trunks are explained in the Trunks chapter.

Addresses and groups are explained in the Addresses and Groups chapter.

Routing Plans

Routing is the process of defining the network topology, assigning addresses to nodes, andassociating these addresses with trunk groups and physical trunks between the nodes. In thisprocess, the paths from each node through the network to every other node is defined for everyvalid endpoint address.

Two types of routing plans are possible:

With hierarchical default routing, the network is structured hierarchically with each topaddressing level consisting of one hub node and many leaf nodes. Each node needs a minimalamount of routing information consisting of what group of addresses are on the directlyconnected nodes only.

With full routing or non-default routing, network topology is not constrained. Each node needsrouting information to determine which of the directly connected nodes is used to reach anyaddress.

Some mixture of these plans is also possible.

Once a routing plan is determined, the mnemonic or numeric representation for each level can bemade. Each address level is assigned to one or more nodes in the network. Typically the toplevel describes the network from an external viewpoint, for example, the country or companyname. Each other level represents a geographical region because each is associated with a groupof physical nodes.

Once addresses are assigned to nodes, routing can be established using the physical trunksbetween the nodes. A trunk group, consisting of a set of physical trunks that go between a pair ofnodes is created. Each trunk group is given a logical name. Associated with each trunk group arethe addresses that can be reached using that trunk group.


Routing________________Default Routing

For large networks, the administration of addresses can become difficult and time-consuming.Default routing provides a method for reducing the work required to administer address changes,additions, and deletions. To use default routing, a network must be organized into a hierarchicalstructure, with hub and leaf nodes at each address level. The following figure shows the basicrelationship of the two node types.

Hub node

Leaf nodeLeaf node

FIGURE 8-1. Hub and Leaf Nodes in a Hierarchy

With default routing, each leaf node only needs to know the addresses of services connecteddirectly to it. These services can be endpoints, or other exchanges or areas. Whenever a nodereceives a call to a known address, it routes the call to that destination. When a leaf nodeencounters a call to an unknown address, it routes the call to its hub node. A leaf node generallyhas only one hub node. (More than one hub is possible, but the advantages of default routingdecrease quickly as the number of hub nodes increases—thus, only configurations with one hubnode per leaf are explained.)

Each hub node must have an address for every attached leaf node. When a leaf node routes a callto the hub node, the hub node determines whether the address belongs to one of its leaf nodes:

If so, the hub node routes the call to the proper leaf node.

If not, the hub node routes the call to the next higher level hub node.

At the exchange level, an exchange hub receives calls routed from exchange leaf nodes, androutes them to other exchange leaf nodes or to the area hub. In other words, it mainly routes callsbetween exchanges in an area. An exchange hub must know how to route to all exchange leafnodes within the same area. If the exchange hub receives a call for an endpoint in another area ornetwork, it routes the call to the area hub.

At the area level, the area hub receives calls routed from area leaf nodes (exchange hubs), androutes them to other area leaf nodes or to the network hub. In other words, it mainly routes callsbetween areas in a network. An area hub must know how to route to all area leaf nodes within thesame network. If the area hub receives a call for an endpoint in another network, it routes the callto the network hub.


Routing________________At the network level, the network hub receives calls routed from network leaf nodes (area hubs),and routes them to other network leaf nodes (area hubs in other networks). In other words, itroutes calls between networks. A network hub must know how to route to all network leaf nodes(area hubs). If the network hub does not find a route for a call, the call fails. It cannot use defaultrouting, since no higher level hub is in the hierarchy.

The following figure shows the relationship of hub and leaf levels in the default routing hierarchy.

_net

_area_area

_exch_exch_exch_exch_exch_exch

_local_local_local_local_local_local

Network hub

Network leaf

Area hub

Area leaf

Exchange hub

Exchange leaf

NETWORK LEVEL

AREA LEVEL

EXCHANGE LEVEL

LOCAL LEVEL

FIGURE 8-2. Hub and Leaf Levels in Default Routing Hierarchy

At each level, a node needs to have certain addresses administered.

At every hub, administer the service addresses for the trunk groups connected to the leafnodes.

At every node, administer the service addresses for every two-way or receiving group in thenode.

At every leaf level node, administer a special service address for each trunk group connectedto the hub node. This service address is used for default routing.


Routing________________The method of administering addresses for default routing involves using a specific name for eachaddressing level. The naming convention is as follows:

At each network leaf, administer the service address of the trunk group to the network hubusing _net for the network level part of the address.

At each area leaf, administer the service address of the trunk group to the area hub using_area for the area level part of the address, and _net for the network level part of the address.

At each exchange leaf, administer the service address of the trunk group to the exchange hubusing _exch for the exchange level part of the address, _area for the area level part of theaddress, and _net for the network level part of the address.

For access to optional services (such as directory assistance) that are not located on the samenode, administer the service address _local to allow a single level dialstring to reach theservice.

The following table shows the information required to administer the network default routinghierarchy using this convention.

TABLE 8-1. Information Requirements for Default Routing at Nodes

_ __________________________________________________________________________Service Addresses_ ______________________________________________________________

Network Leaf Area Leaf Exchange LeafNode Level

(Area Hub) (Exchange Hub) (Local Node)Local Endpoint

_ ___________________________________________________________________________ __________________________________________________________________________Network Hub Path to all — — —

network addresses_ __________________________________________________________________________Area Hub _net Path to all areas — —

in the network_ __________________________________________________________________________Exchange Hub _net _area Path to all exchanges —

in the area_ __________________________________________________________________________Local Node _net _area _exch All local addresses

in the exchange_ __________________________________________________________________________


Routing________________When all three levels of default routing are defined, the selection of routing for a call follows thelogic shown in the following table.

TABLE 8-2. Routing Choices for Nodes at Each Level

_ ______________________________________________________________________Routing at Exchange Leaf Node_ ______________________________________________________________________

[<own_network>/][<own_area>/][<own_exchange>/]<endpoint> → <local_endpoint>[<own_network>/][<own_area>/][<own_exchange>/]<unknown_endpoint> → _local

[<own_network>/][<own_area>/]<unknown_exchange>/<> → _exch

[<own_network>/]<unknown_area>/<>/<> → _area

<unknown_network>/<>/<>/<> → _net_ ______________________________________________________________________Routing at Exchange Hub Node (Area Leaf Node)_ ______________________________________________________________________

[<own_network>/][<own_area>/]<local_exchange>/<> → <local_exchange_leaf>[<own_network>/][<own_area>/]<unknown_exchange>/<> → REJECTED

[<own_network>/]<unknown_area>/<>/<> → _area

<unknown_network>/<>/<>/<> → _net_ ______________________________________________________________________Routing at Area Hub Node (Network Leaf Node)_ ______________________________________________________________________

[<own_network>/]<local_area>/<>/<> → <local_area_leaf>[<own_network>/]<unknown_area>/<>/<> → REJECTED

<unknown_network>/<>/<>/<> → _net_ ______________________________________________________________________Routing at Network Hub Node_ ______________________________________________________________________

<local_network>/<area>/<exchange>/<endpoint> → <local_network_leaf><unknown_network>/<area>/<exchange>/<endpoint> → REJECTED_ ______________________________________________________________________

The effect of default routing on security depends on the type of security check being enforced.See the Security chapter for details.

Depending on network needs, the default address option and hierarchical network organizationcan be implemented in some subset of the address levels: local, exchange, area, and network.Once default routing is established, whenever a new network, area, or exchange node is added,the administrator only needs to enter the information into the database of the appropriate hubnode.


Routing________________Full (Non-Default) Routing

For small networks, a nonhierarchical network topology might be sufficient. In these cases, notall levels in the addressing hierarchy are needed. An example of this type of routing is shown inthe following figures where a ring and a mesh topology are used.

NodeB

NodeC

NodeA

NodeD

1 2

1

2

1

3

2

3

2

1

FIGURE 8-3. Non-Hierarchical Network Example

Many choices are available for assigning addresses to individual nodes. One simple choice is toassign a different exchange to each node. Routing choices could then be made on the exchangelevel only. Each node would have to know which trunk is the path to each other exchange in thenetwork. But note that multiple paths can be used to reach every node.


Routing________________Using the ring network as an example, each node can route the call clockwise orcounterclockwise to reach every other node. A general recommendation is to have each nodetraverse the fewest number of nodes as its primary path. The primary paths for nodes A and B areshown in the following table.

_ ________________________________________Originating Primary Destination

Node Trunk Group Node_ _________________________________________ ________________________________________A Trunk Group A-B B or C

A Trunk Group A-E D or E_ ________________________________________B Trunk Group B-A A or E

B Trunk Group B-C C or D_ ________________________________________

Similar assignments are made for other nodes in the network. See the Alternate Routing sectionfor information about planning other paths in the network.

Trunk Groups

Once addresses are assigned to nodes, routing can be established using the physical trunk betweenthe nodes. A trunk group consists of a set of physical trunks that traverse a pair of nodes. Eachtrunk group is given a logical name. Associated with each trunk group are the addresses that canbe reached using that trunk group. Optionally, security patterns can also be associated with eachtrunk group.

Remote exchanges, areas, and network addresses are associated with a trunk group. Any localaddress for a connected end device on another node in the same exchange also points to a trunkgroup. Trunk groups contain trunk modules only and one trunk group can contain one or moretrunk modules.

The following figure shows two trunks going to the same node. Here, the trunks are typicallyassigned to the same trunk group. If round-robin is enabled per module, the calls are alternatedover the trunk modules in the group.


Routing________________

TrkgrpAB

TrunkModule

B1

TrkgrpBA

TrunkModule

B2

TrunkModule

A2

TrunkModule

A1NodeA

NodeB

FIGURE 8-4. Two Trunks to the Same Node

The following figure shows three trunks in Node A, each going to a different node. Here, forproper routing, each trunk is assigned to a unique trunk group.

TrunkModule

A3

TrunkModule

A2

TrunkModule

D1

NodeD

TrkgrpDA

NodeC

TrkgrpCA

NodeB

TrkgrpBA

TrunkModule

C1

TrunkModule

B1Trunk

ModuleA1

TrkgrpAD

TrkgrpAC

TrkgrpAB

NodeA

FIGURE 8-5. Three Trunks to Different Nodes


Routing________________Alternate Routing

During call setup, each node between the originating and destination endpoints of a call mustchoose a path that the call is to take to the next node. If sufficient trunk groups are administered,the network administrator can define up to four trunk groups as paths between any node and anadjacent node. During call setup processing, the routing algorithm chooses the primary trunkgroup or one of the alternate trunk groups as the path to the next node.

When designing the routing plan, spare trunks and redundant paths should be considered. Twotypes of redundancy can be provided using alternate routes:

multiple physical trunks in a trunk group

multiple trunk groups through multiple nodes

These alternate routing options are shown in the following figure.

A

B

C

D

E

Ring Network Topology

A

B

C

D

E

Mesh Network Topology

FIGURE 8-6. Alternate Routing Example


Routing________________The redundant path is provided between NodeA and NodeB by using multiple physical trunks inthe trunk group. Two physical trunks, which are between NodeA and NodeB, consist of trunkA1 to B1 and trunk A2 to B2. This configuration provides protection against trunk module andtrunk facility problems. Assuming Node B contains all endpoints in exchange B, then node Acan define the following routing assignment:

Call originates at Node ADestination address = <Exchange B>/<any endpoint>Choose trunk group = trkgrpABTrunk A1 to B1 and trunk A2 to B2 = trkgrpAB

where: the trunk selection algorithm can be configured asround-robin or primary/secondary

Alternate routing using multiple trunk groups is also shown in this example network. Node A canreach Node D two ways: through the trunk group to Node B and through the trunk group toNode C. Assuming Node D contains all endpoints in exchange D, then node A can define thefollowing routing assignment:

Call originates at Node ADestination address = <exchange D>/<any endpoint>Choose trunk group = trkgrpAB or trkgrpAC

where: the trunk group selection algorithm can be configuredas round-robin or primary/secondary.

Trunk A1 to B1 and trunk A2 to B2 = trkgrpABTrunk A3 to C1 = trkgrpAC

Nodes B and C have a similar routing assignment—to route the call to node D.

If routing is not properly designed, call looping can result. Data Networking Products nodesenforce some simple routing path restrictions that make it easier to plan routing. For example,each node does not allow a call to be routed back to the same trunk group. This restrictionprohibits loops from occurring between a pair of nodes that are connected by a single trunk group.It does not prohibit other types of loops.


Routing________________The following design rules and the use of alternate routing options can help to design a networkthat does not use default routing. When designing redundant paths, follow these rules:

The primary route should go through the least number of nodes.

If a node can be reached via two routes and each route goes through the same number ofnodes, consider the transmission speed of the two trunks. Use the path with the greaterbandwidth as the primary route.

Consider the volume of traffic when selecting the trunk transmission speed and the number ofroutes.

Options

The routing algorithm includes two options that can improve call routing performance undercertain conditions. These options are called extended routing and hop count.

Extended Routing

With the standard routing algorithm, two conditions can block a call from getting through:

A trunk is not available to the next node.

This condition can occur if, at any node along the route, none of the alternate trunks can beused. The standard routing algorithm would reject the call at that point even if paths wereavailable through other nodes. The extended routing option can counter this condition bydropping the call back to the originating node and trying an alternate route from theoriginating node. This concept is called crankback.


Routing________________The following figure shows an example of a routing problem that the crankback function cansolve.

P= Primary RouteS = Secondary Route

N6

N5

N2

N3

N1L6 L1

P

L5 L2

N4L4

S

L3 Source

P

FIGURE 8-7. Crankback

1. A call is placed from node N3 to node N1.

2. The call is routed initially via the primary path along trunk L2 to node N2.

3. From node N2, the path is via trunk L1 to node N1.

4. The secondary path from node N3 to node N1 goes through nodes N4, N5, and N6.

5. The call from node N3 comes into node N2 on trunk L2. Its destination is node N1.

6. If trunk L1 fails, the call cannot be routed via that trunk, so the routing algorithm attempts touse the secondary path.

7. The secondary path uses trunk L2. However, since the call entered the node on trunk L2, itcannot be routed out of the node on that trunk.

8. At this point, crankback drops the call back to node N3. From node N3, the call is routedthrough the secondary path, which is trunk L3. Using that path, the call reaches thedestination node.


Routing________________The routing algorithm selects a trunk to the next node, but it is the same trunk through whichthe call entered.

This condition can occur when a call is rerouted through an alternate trunk. The reroutingcould cause a call to enter a node through a trunk that would normally be used as an outgoingtrunk to the final destination. If the call comes into the node on the same trunk as the primaryoutgoing trunk, the standard routing algorithm rejects the call. The extended routingalgorithm chooses the next alternate trunk, if one exists, and tries it instead. This concept iscalled route advance.

The following figure shows an example of a routing problem that the route advance functioncan solve.

P= Primary RouteS = Secondary Route

N6

N5

N2

N3

N1L6 L1

P

L5 L2

N4L4S

P

SL3

Source

FIGURE 8-8. Route Advance

1. Trunk L3 is the primary path from node N4 to node N1.

2. If trunk L1 is down, as in the first example, a call from node N3 to node N1 is rerouted to nodeN4.

3. When this call reaches node N4, the standard routing algorithm would normally select trunk L3as the path for routing the call.

4. Because the call entered the node on trunk L3, it cannot leave on L3.

5. At this point, route advance selects trunk L4 because it is the secondary path to node N1. Thecall setup request reaches its destination on that path.


Routing________________Hop Count

In some network configurations, a call could be routed through an endless series of alternateroutes without ever reaching its destination. Call looping is the term for this condition. To avoidthis problem, analyze the network configuration and alternate route selection carefully. In morecomplex configurations, loops may be impossible to avoid. A loop may exist in the network iferror messages are appearing in these situations:

Asynchronous terminal users are receiving the following message:

Connection not completed. Contact Network Administrator. (45, <node>)

In the message, <node> is the name of the node where the limit is reached.

Predefined Destination (PDD) terminal call failures are sending the following message to thenetwork administrator:

** 8456 MODADDR=<addr> CHANNEL=<num> MODTYPE=<type>

REPORT FAILURE: Too many invalid attempts. Predefined destination

out of service or busy.

STATION=<station id> REASON=45 NODE=<node>

In the message, <node> indicates the name of the node where the limit is reached,<station id> indicates the originating endpoint for the PDD, and <addr>, <num>, and<type> indicate the destination.

Fortunately, the hop count option provides a method to limit call looping. To use it, a networkadministrator must specify the maximum number of nodes that a call request can pass through onthe way to its destination. This number is called the hop count. It allows the routing software tocount the number of nodes that a call request has crossed, or the number of hops. When a callrequest loops, it eventually exceeds the number of hops in the hop count, and it is rejected.

The hop count is administered at each originating node. To determine the value for the hop countfor each node in the network:

Find the longest path from that node to any destination that can be called from that node.Measure the length of the path by counting the number of nodes crossed.

Use the length of the longest path as the hop count for that node.

For large networks with complex alternate routes, this method may not be feasible. A generalsolution is to subtract 1 from the number of nodes in the network and use the result as the hopcount. This value may be too large for hierarchical networks, so a smaller value might have to bechosen. The largest possible value for the hop count is 99.


Routing________________Interworking

In a network containing Datakit II VCS Release 2.0 (or earlier) nodes or BNS-1000 Release 1.0or later nodes, or a network upgraded to Datakit II VCS Release 2.1 or later, review the existingrouting tables before administering extended routing. Carefully analyze networking routingassignments to avoid call looping problems. Although the hop count option limits call looping, itdoes not prevent it completely. Use the following guidelines:

If the network has three nodes or less, do not administer extended routing.

If the node’s call transition rate is close to capacity, do not administer extended routingbecause the capacity of the Control Computer could be affected if a significant number ofcalls are being rerouted because of trunk failures. The call transition rate includes thefollowing events:

— Call setup occurs when a call is established from an originating endpoint to a destinationendpoint.

— Call takedown occurs when an established call ends.

— Splice occurs when a call is routed to an initial destination (security server), which thenforwards the call to its final destination. When the second call is established, the initialdestination splices the two calls together and removes itself from the path.

For a ring network with more than three nodes, administer extended routing for all BNS-2000and BNS-2000 VCS nodes, and for nodes running Datakit II VCS Release 2.1 (or later) orBNS-1000 Release 1.0 (or later) software. For all other networks, detailed analysis should beperformed before administering extended routing. (A ring network is a network in whicheach node has trunk connections to exactly two other nodes.)

A fully connected network does not require extended routing. To reduce the number of trunksin a fully connected network, redesign the network and administer extended routing to routecalls between nodes. (A network is fully connected if every node has a direct trunkconnection to every other node.)

If, during an iteration of the node command, the ACTIVATE EXTENDED ROUTINGFEATURE is administered as no, it must also be administered as no for each BNS-2000Release 1.0 (or later), BNS-2000 VCS Release 6.0, Datakit II VCS Release 2.1 (or later), orBNS-1000 Release 1.0 (or later) node in the network. When extended routing is administered(yes), the node hop count function, as specified in the MAXIMUM HOP COUNT PER CALLprompt, must also be administered with a value from 3 to 99.


Routing________________For the enhanced routing algorithms (hop count, crankback, and route advance) to functionproperly, all nodes in the network must be running BNS-2000 VCS Release 6.0 or Datakit IIVCS Release 2.1 or later. For Datakit II VCS pre-Release 2.1 nodes, the following exceptions tothe hop count feature occur:

When a call request crosses a Datakit II VCS Release 2.0 node, the hop count is preserved,but it is not decremented.

When a call request crosses a Datakit VCS node or a Datakit II VCS Release 1.0 or 1.1 node,the hop count is dropped.

When a call crosses these nodes, the hop count function does not function properly.

If a call setup fails at a Datakit II VCS Release 2.0 or earlier node because a trunk was removedfrom service, crankback is not invoked. Similarly, if a call setup fails at a Datakit II VCS Release1.0 or Datakit VCS node because trunk channels were not available, crankback is not initiated. Ifa call setup fails at a BNS-2000 node, BNS-2000 VCS node, or a Datakit II VCS Release 2.1 (orlater) node, crankback is initiated if a trunk fails, is removed from service, or does not have anyavailable channels. crankback is not initiated for any other call failures.

For route advance to function properly, the node where route advance occurs must be aBNS-2000 Release 1.0, BNS-2000 VCS, or Datakit II VCS Release 2.1 (or later) node. Othernodes in the network can be Datakit II VCS Release 2.0 (or earlier) nodes.

Lucent Technologies can provide assistance with the Extended Routing Analysis Service. Forinformation, contact your Lucent Technologies Account Team.


________________Security

Overall Security Planning 9-3Determine Security Requirements 9-4Conduct the Vulnerability Analysis 9-4

Security Features 9-6Console Security 9-6Network Access Restriction 9-6Originating Group Security 9-7Security Pattern Examples 9-10Select Group Feature 9-11Call Screening 9-11CUG Security 9-14X.25 Incoming/Outgoing Calls Barred 9-19X.75 Security Features 9-20Network Access Control System 9-22DKAP Security Software 9-24Network Security and LAN Interconnection 9-26LPM Security 9-26Default Routing and Security 9-27

Security Planning Examples 9-27Originating Group Security Example 9-27CUG Security Example 9-30Trunk Call Screening Example 9-33


________________Security

The network design provides latitude for implementing network security. Depending on thesecurity needs of the network and applications, network nodes can enforce restrictions on thefollowing:

access to the node console

access to the network DESTINATION: prompt

access to each destination according to the originating group identity

incoming and/or outgoing calls to closed user group (CUG) members

calls between CUGs and the open network

calls originating from a CPM or outgoing on a trunk

These restrictions can be combined with other security measures to provide more open orrestricted access as needed to the group or endpoint level.

Other aspects of security are treated elsewhere as follows:

Security specific to SMDS is explained in the BNS-2000 SMDS Guide. In particular, note thatthe term screening, as it is used in trunk and CPM call screening, does not have any impact onSMDS address screening.

An overview of how security relates to physical units (the hardware), local and trunk groups,routing, and addressing is provided in the Connection-Oriented Network Services chapter.

Overall Security Planning

As users and devices are added to a network, opportunity for unauthorized access to the networkis increased. While designing the physical and logical configuration of the network, theappropriate level of security for the network can be specified. With proper planning, the overallsecurity of the network can be enhanced and the chance of intrusion minimized.

A single system or series of systems cannot deter all attempts at unauthorized access or preventall natural hazards. Therefore, evaluate control measures in terms of their resilience and deterrenteffect. Implementing any security measure increases the amount of work required to gainunauthorized access to a network, which increases chances to detect such attempts, and to defeatthem if at all possible.

The support of senior-level management is crucial to the planning and implementation of securityfeatures at every level.


Security________________The steps involved in planning network security include the following:

determine security requirements

conduct a vulnerability analysis

plan security measures using the security features described in this chapter

Determine Security Requirements

Establishment of a security planning team is the first step in implementing a total security system.The planning team, comprised of individuals from several internal groups, should gatherinformation on the following:

hardware components and configuration

software components and configuration

programming personnel and assignments

end-user personnel and assignments

data types and processing flows

input/output documents

procedures

Other analyses should include the importance of data applications and the sensitivity levels of alldata within the company.

Conduct the Vulnerability Analysis

If conducted properly, a vulnerability analysis supplies answers to the questions that may arise inthree major areas: physical security, personnel security, and operational security.

Physical Security

A computer communications network is subject to a wide variety of threats and hazards that mayoften be countered by physical controls. Examples include:

deliberate intrusions (theft, fraud, sabotage)

accidental loss (incompetence, curiosity, interruptions)

natural hazards (fire, earthquake, flood)

utility outages (power, steam, sewer)

Prevention measures should include access controls, fire-fighting systems, specialconstruction/renovation features, and backup utility systems.


Security________________Personnel Security

The level of communications network security achieved by an organization is largely the result ofgood personnel practices in areas such as selection, training, and supervision.

Operational Security

Security planning should consider some of the more common lapses that occur in the networkenvironment. These include:

Failure to upgrade standard vendor security provisions. Many vendors use standard, factorysettings when they install equipment and software with security features. These settings ofteninclude standard passwords. It is important to change these settings to values known only tothe appropriate personnel. One of the most common methods of gaining unauthorizednetwork access is through standard passwords that were never changed after installation.

Lack of password aging and expiration. Even secure passwords can be learned in time, eitherthrough eavesdropping or through trial-and-error attempts. A good security practice is to setyour host computer systems to periodically require new passwords for continued access.

Inclusion of passwords found in dictionaries. Many systems use known password encryptionalgorithms, and keep the encrypted passwords in areas of the system that are accessible tousers. A common method of penetrating such systems is to feed terms from an on-linedictionary through the encryption algorithm and try to match one of the encrypted passwords.One way to foil this type of attack is to ensure that a password is never a word that can befound in a dictionary. This method is accomplished via a program that generatespronounceable (and memorable) random character strings for users to select as passwords.

Repeated use of plaintext passwords. The plaintext (unencrypted) form of a password shouldnot be handled within the network. For instance, updated access passwords should becommunicated to users by trusted communications channels other than the network itself.


Security________________Security Features

The network offers a wide variety of security features that can operate independently of eachother or in concert. Each feature has advantages for certain types of access control in a network.These security features include the following:

console security

network access restriction

originating group security

select group feature

call screening

CUG security

X.25 incoming/outgoing calls barred

X.75 CUG indication, access indication, and traffic agreement checking


DKAP security software

LPM security

The security design for the entire network is essential; a piecemeal approach could risk leavingcompromising loopholes. However, these features are administered separately for each node. Toassemble a security plan for the whole network, how each security feature operates in one node,and how it operates for several nodes must be understood. How the security features interactwhen combined must also be understood.

Console Security

The console security feature allows an administrator to configure a password for theadministrative port (port A, port B, or port M) to restrict access. If a password is not configured,the node does not restrict access to the port. A password can be added using enter node orchange node.

Network Access Restriction

The basic principle for network access restriction is that every device attached to the networkmust belong to a group. A device used to originate calls must belong to an originating or two-way group. Each originating group or two-way group can be assigned a password. The networkadministrator can require a user to provide this password before the node displays theDESTINATION: prompt and allows the device to originate any calls. The following figure showsthe basic concept.


Security________________

CallOriginator

NetworkNode

NetworkAccess

Restriction

FIGURE 9-1. Network Access Restriction

This feature is optional, since not every situation dictates the use of a password. For instance, aterminal in a secure location that is configured to make only predefined destination (PDD) callsmight not need an access password. On the other hand, a port connected to a dial-in modem withaccess to the destination prompt definitely should have an access password or use the NACSystem.

The network supports a maximum number of 2048 groups per node. More than one person canuse one originating group and share the same password. However, the more people who knowand share a password, the greater are the chances that the password may be disclosed to anunauthorized person.

Originating Group Security

During call establishment, every switched call must specify a valid destination. This enables thenetwork administrator to set controls at each destination (and at tandem nodes along the route of acall) to specify exactly which calls are to be accepted or rejected.

Originating group security depends on assigning each potential call originator to an originatinggroup or two-way group. As its name suggests, an originating group consists of one or moreendpoints that can originate calls. An endpoint in a two-way group can both originate and receivecalls.

A call destination is assigned to a receiving group (or two-way group), which is assigned aservice address at which it receives calls. Each service address can be set to grant or deny accessto each caller, depending on the caller’s originating group identity. The following figure showsthe effect of originating group security.


Security________________

CallDestination

NetworkNode

OriginatingGroup

Security

Receiving groupor two-way group

CallOrigin

Originating group ortwo-way group

FIGURE 9-2. Originating Group Security

The network administrator controls the effect of call restrictions in two ways: by assigningendpoints to originating groups, and by specifying the originating group security patterns for eachservice address.

Originating group security applies only to calls to SVCs and PDDs between endpoints in differentnodes. PDDs between endpoints connected to the same node are not subject to originating groupsecurity. In this case, the network administrator should be certain that other security measureswill provide adequate protection before defining these PDDs.

Originating Group Security and Default Routing

If default routing is used in the network, allow for its effect on originating group security.Originating group security checking is done after the default routing address is substituted. Thus,each default address must have originating group security patterns entered to accommodate thepotential call originators.

Originating and Receiving Groups

Call originators belong to originating groups or two-way groups (that can place and receive calls).Call destinations belong to receiving groups, two-way groups, or trunk groups. Each group mustbe assigned a service address by which call originators can specify it as a destination. Eachservice address can have a security pattern defined for it that specifies exactly which originatinggroups are allowed access and which are not. If the network administrator does not specify asecurity pattern for a service address, it will not have call restriction security.

The network administrator should establish security requirements by determining whichoriginating groups may have access to each service address. Once these requirements are defined,they can be entered for each service address by means of an originating group security pattern.


Security________________Originating Group Security Patterns

An originating station does not have an originating group name assigned to it automatically. Thenetwork administrator must administer the group name for each station. Whenever a call isattempted, this name is passed to the destination (and to tandem nodes along the route) as part ofthe call setup message (along with the service address of the node from which the call isoriginated).

An originating group security pattern provides a mechanism for defining whether to permit ordeny access to a service address from a particular originating group. The feature works bycomparing the originating group name to a character pattern, and determining whether it matchesthe pattern. The network administrator enters these patterns into the database. Originating groupsecurity patterns can have up to 67 characters. If none is entered as the security pattern for aservice address, all originating groups have access to that destination. The security pattern maycontain letters, digits, and special characters, as shown in the following table.

TABLE 9-1. Special Characters used in Originating Group Security Patterns

_ ________________________________________Character Meaning_ _________________________________________ ________________________________________

! "Not" (access denied)_ ________________________________________* Matches any number of characters_ ________________________________________? Matches any single character_ ________________________________________

[a-z] Matches any single character

in a range of characters

(in this example, any letter from a to z)_ ________________________________________[abdghmkptvx] Matches any single character

in a set of characters (in this

example, any letter listed)_ ________________________________________

Security patterns can use multilevel addresses. Each address level can be up to 16 characterslong. If a security pattern specifies only a local address, the network, area, and exchange of thelocal node are implied. Any part of the address that is not specified explicitly is completed fromthe full address of the local node. For instance, if the local node address is usa/denver/nw01, thelocal address anyaddr is assumed to mean usa/denver/nw01/anyaddr. Note the effect that this hason the ! (access denied) character: if !group is entered as the originating group security patternfor a local address, it implicitly means !usa/denver/nw01/group, which would allow access to anyoriginating endpoint in the entire network except originating endpoints in the local group group.


Security________________Security Pattern Examples

This section shows some examples of security patterns and explains the effect of each pattern onaccess to the corresponding service address. For the sake of these examples, assume that the localnode address is usa/cb/compctr. Here are some ways security patterns can be used for variousaccess control needs:

The tradmin group needs to access the service address train. No other groups are allowedaccess.

Service address: trainSecurity pattern: tradmin

Allow all groups, except local groups beginning with acct, to access the service address devel.

Service address: develSecurity pattern: !acct*

All groups in this network whose names begin with acct can access service address budget,except groups whose names end with trn.

Service address: budgetSecurity pattern: */*/acct*,*/*/!*trn

All groups in the exchanges usa/cb/compctr and usa/east/dev can access news.

Service address: newsSecurity pattern: usa/cb/compctr/*,usa/east/dev/*

All groups except those in the local exchange whose group name begins with scc can accessdb1. Groups from other nodes are allowed access even if the last part of their name beginswith scc.

Service address: db1Security pattern: !scc*

All groups whose name begins with scc (except those in the compctr exchange) can accessdb2. This restriction applies whether the group is in the local node or in another network, areacode, or exchange.

Service address: db2Security pattern: */*/!compctr/scc*


Security________________Select Group Feature

The select group feature allows a user to change to a new originating group name during asession. This feature can be disabled or enabled for each node. The administrator must require apassword to be entered prior to allowing a user to acquire a new group identity. By selecting anew group identity, the user acquires the calling permissions of the new group. This provides anadded measure of flexibility in assigning originating group security to protect access to variousendpoints in the network.

Call Screening

The call screening feature enables a network administrator to administer a profile that defines asecurity pattern to be used by an internodal connection-oriented trunk or CPM-connected host.This security pattern, which is an alphanumeric string exactly like those used in originating groupsecurity, is compared to the destination address of the call originating on a node or host.

The destination address of the incoming call from a host or a call outgoing on a trunk is examinedfrom the beginning of the address, through and including the "." (that is, the period, if the patternincludes a period), and any characters that follow in the destination string. This destinationaddress is compared to the administered call screening security pattern contained in the profile. Ifthe destination address matches an allowed pattern, and it does not match a prohibited pattern, thecall is allowed to go through.

Each internodal trunk module or CPM-connected host can be assigned a call screening profile andthe same call screening profile can be assigned to more than one trunk or CPM. If a callscreening profile is not assigned to a trunk or CPM, call screening does not occur for anyincoming calls from other nodes or hosts.

The following examples show how call screening security patterns work:

If calls originate on Host A and go over Trunk A-B to get to Host B and if Trunk A-B has acall screening profile of sna[1-3], then calls to sna1, sna2, and sna3 can be made over TrunkA-B.

Security pattern: sna[1-3]

If calls originate on Host A and are destined for service address lam, cal01, cal02, and cal03and if the CPM has a call screening profile of !la*, cal0[1-3] associated with it, then cal01,cal02, and cal03 are allowed to originate from this host, but lam is blocked.

Security pattern: !la*,cal0[1-3]

Note that speedcall addresses are checked before expansion. If a speedcall address passessecurity, the call is accepted, even if the expanded address would be rejected.


Security________________The following figure shows the effect of call screening security at the node level.

Trunk CallScreening

CallDestination

Host B

CallOriginator

Host A

NetworkNode

Node A

NetworkNode

Node B

Trunk A — B

CPM CallScreening

FIGURE 9-3. Call Screening Security

Performance Considerations

When a call enters a trunk or CPM-connected host with a call screening profile administered, itsdestination address is screened against the call screening profile. In general, the screening logicsearches the entire profile until one of the following conditions occurs:

The call destination matches a forbidden pattern. If a forbidden pattern is found, the searchstops immediately.

The whole profile is searched without finding a forbidden pattern. If a forbidden pattern is notfound, the search continues until every pattern in the profile is checked to determine if itallows or forbids each call.

This searching logic has consequences for call processing. Nodes operating at or near therecommended limit of call transitions (call setups and takedowns) for CONS traffic shouldseverely restrict their use of trunk call screening security.

First, the most efficient way to screen calls is by specifying forbidden destinations because assoon as one is matched, the search is abandoned. Second, the size of the call screening profile issignificant because it is searched exhaustively in many cases. Therefore, the following guidelinesare important to follow when administering call screening security profiles:


Security________________To avoid significant impact on call setup time, avoid using call screening profiles with morethan 100 patterns. If possible, use call screening profiles with more than 100 patterns only atdestination nodes (where, for example, destination host computers are attached).

This guideline applies especially to tandem nodes (with no local endpoints). Since all callsthrough tandem nodes enter via trunks, potentially every call through a tandem node could bescreened. To a lesser degree, this guideline also applies to intermediate nodes (which havelocal endpoints). Because some of the traffic in an intermediate node is not subjected to trunkcall screening, it may be less vulnerable to slowdown from processing large call screeningprofiles.

Always put forbidden patterns at the beginning of the profile. (Remember—a match with aforbidden pattern stops the search.)

If possible, screen full destination addresses only at the node to which they are connected, andscreen only area and exchange addresses for other nodes.

In hierarchical and mesh networks, use forbidden patterns to refer to the addresses of trunks toother nodes. Avoid using patterns that refer to destination addresses in other nodes.

In ring networks, limit profiles to forbidden patterns for addresses in the local node, followedby patterns for other area and exchange addresses. Avoid using patterns for addresses in othernodes.

To reduce the size of profiles, use patterns rather than specific addresses whenever possible.

Avoid duplicate patterns or patterns that are subsets of other patterns.

Check profiles regularly and delete unused patterns.

Trunk Call Screening and Default Routing

If default routing is used in the network, the trunk call screening security must allow for the waycalls are rerouted through hubs. When a call is routed to a hub node by default routing, it issubjected to trunk call screening security in the hub. Each trunk into a hub node from a leaf nodemust have a call screening security profile to accept calls routed to it by default routing. In thesame way, the destination node will receive calls via its trunk connection to the hub node, and itmust have an appropriate call screening profile for these calls.

Trunk Call Screening Interworking

Trunk call screening works only on nodes running BNS-2000 Release 2.0, BNS-2000 VCS, orDatakit II VCS Release 2.1 or subsequent releases, and it works regardless of the release level ofthe node connected to the other end of the trunk.


Security________________CUG Security

CUG security enables an administrator to define groups of endpoints that restrict access to orfrom endpoints outside the group. It is available for endpoints placing calls to an X.25 host,PAD, or PDN endpoint, or for endpoints receiving calls from an X.25 PDN, or X.25 host. CUGsecurity may also be used between asynchronous endpoints. It is implemented as a set of X.25and X.75 facilities, as defined in CCITT Recommendations X.25, X.28, X.75, and X.3 (1988).The following closed user group facilities are supported:

CUG

CUG with incoming access

CUG with outgoing access

CUG selection

CUG with outgoing access selection

Effect of CUGs

The effect of using CUGs can be shown with a few simple figures. In these figures, the node isomitted to make the relationships clear.

The following figure shows the effect of CUGs on calls between nodes inside and outside of aCUG.


Security________________Closed user group

Open Network

A can call BB can call AC cannot call A or BA and B cannot call C

C

BA

FIGURE 9-4. CUG Security


Security________________The following figure shows the effect of a CUG where one endpoint has incoming access.

Closed user group

Open Network

A can call BB can call AC can call B (incoming access)

A and B cannot call C

BA

C

FIGURE 9-5. CUG with Incoming Access


Security________________The following figure shows the effect of a CUG where one endpoint has outgoing access.

Closed user group

Open Network

A can call BB can call AB can call C (outgoing access)

C cannot call A or B

BA

C

FIGURE 9-6. CUG with Outgoing Access

CUG Profiles

To use CUG security, each endpoint, hunt group, and gateway is configured with a CUG profile.(A hunt group is a logical concept that applies to a group of destination endpoints for whichincoming calls are assigned to the first available endpoint.) An endpoint can be a port on anasynchronous interface module, a port on a standards interface module, or a channel on amultiplexed host interface.

The CUG profile contains information used during call processing to determine which CUG toassociate with the endpoint, and whether to allow outside access. The CUG profile contains thefollowing information:


Security________________CUG identifier is a number between 1 and 255 that represents each CUG. A CUG identifier ismeaningful only within the network in which it is defined.

The CUG profile contains a list of CUGs to which an endpoint, hunt group, or gatewaybelongs. The CUG profiles for an endpoint may have up to 20 CUG identifiers, and the CUGprofile for a gateway may have up to 99 CUG identifiers. An endpoint may select one CUGfrom the list when originating a call.

Preferential CUG is the default CUG to use when a CUG is not selected for a call. If aterminal, host, or hunt group accesses X.25 services, it must have a preferential CUGconfigured; it is optional for gateways.

Outgoing access permission allows an endpoint that belongs to a CUG to originate calls toendpoints outside the group, including endpoints that do not have CUG security configured(known as the open part of the network) or endpoints in other CUGs that have incomingaccess permission.

Incoming access permission allows an endpoint that belongs to a CUG to receive calls fromoutside the group, including endpoints in the open part of the network and endpoints in otherCUGs that have outgoing access permission.

In some cases, an endpoint can have more than one associated CUG profile. For example, anendpoint can be a member of a hunt group with a CUG profile. An endpoint can also have itsown assigned CUG profile. If the endpoint initiates a call to a switch endpoint, it may also havea CUG profile associated with the gateway to the switch. An X.25 host port can select the CUG ituses for a call as well as the outgoing access permission (if it is administered for the port). If theendpoint does not select them explicitly, the call processing logic selects the CUG profile andaccess permissions according to the circumstances of each call.

CUG and Outgoing Access

An asynchronous endpoint originating a call through an X.25 PAD in a node can use an X.28CON command to select the CUG identity for the call, provided the endpoint is administeredwith more than one CUG in its profile. If a CUG is not selected, and more than one CUG isconfigured in the CUG profile, the system selects the preferential CUG; meaning, a givenendpoint may have access to any CUG in its CUG profile.

If the CUG profile associated with an endpoint has outgoing access permission administered, theendpoint can call destinations in other CUGs (provided they have incoming access permission) orin the open part of the network.

CUG Security Checking Rules

The first stage of CUG security checking is done at the originating end of the call. It consists ofchecking the selected CUG facilities against the CUG configuration options for the originatingendpoint. Also during this stage, the software determines values for the selected CUG index andother options to be sent to the destination end.

The second stage of CUG security checking is done at the destination end of the call. The selectedCUG facilities are matched to the destination CUG profile and incoming access permissions.


Security________________CUG security checking is done on the local level default address, if one is used. If CUG securityis used, and if the default address in a given node is a CUG member, its CUG profile mustaccommodate possible originators, which requires a thorough analysis of potential call originatorsand destinations.

CUG Security Selection for Non-X.25 Calls

For BNS-2000, user selection of the CUG identity is provided for calls to or from the PADservice, X.25 host, or PDN endpoints. For Datakit II VCS, user selection of the CUG identity isprovided only for calls to the PAD service, to X.25 calls from X.25 host or PDN endpoints, orfrom hosts using a multiplexed host interface. For calls from asynchronous endpoints not usingthe PAD service, CUG selection is done by comparing the originating CUG profile to thedestination CUG profile.

X.25 Incoming/Outgoing Calls Barred

X.25 and X.25P ports have a feature available that allows the network administrator to prevent anendpoint from originating or receiving calls. This is an implementation of the following X.25facilities:

incoming calls barred

outgoing calls barred

These facilities can be used to restrict switched virtual circuit (SVC) calls into or out of X.25endpoints. Without these restrictions, the endpoints normally have both incoming and outgoingSVC access.

The following illustrates how the terms incoming and outgoing are defined with reference to aPDN and an X.25 host.

When an X.25 host is connected directly to a PDN, the host appears to the PDN as DTE, andthe PDN appears to the host as DCE. In that context, incoming refers to incoming calls fromthe PDN (DCE) to the host (DTE), and outgoing refers to outgoing calls from the host (DTE)to the PDN (DCE).

When an X.25 host connects to a node, the node appears to the host as DCE, and to the PDNas DTE. The relative directions of incoming and outgoing calls are the same as in a directconnection from host to PDN.


Security________________

OUTGOING CALLS BARRED

incoming incoming

PDNNetwork

NodeX.25host

INCOMING AND OUTGOING CALLS ALLOWED

outgoing outgoing

incoming incoming

PDNNetwork

NodeX.25host

outgoing outgoing

PDNNetwork

NodeX.25host

INCOMING CALLS BARRED

FIGURE 9-7. Incoming and Outgoing Calls Barred

X.75 Security Features

Data Networking Products nodes include security mechanisms in compliance with CCITT X.75.

X.75 CUG Indication

X.75 CUG with Outgoing Access Indication

Check of Traffic Agreements for Incoming Calls


Security________________CUG Indication

X.75 protocol supports CUGs, which provide a security mechanism by which the network, onbehalf of the destination endpoint, accepts or rejects calls from an originating endpoint. CUGsecurity for the X.75 module is based on a CUG-mapping table (cmap) where a one-to-onecorrespondence is established between the international 32-bit field for CUGs, which is referredto as an international interlock code (ICN), and the network’s existing 8-bit field for CUGs.

The CUG indication is used for enabling the establishment of virtual calls by DTEs that aremembers of international CUGs. Here, the use of CUGs differs from that in the X.25 PDNfeature. The X.25 PDN gateway is considered an endpoint on the Data Networking Productsnetwork and virtual circuits can be assigned an endpoint number and CUG. However, the X.75gateway just maps international CUGs to Data Networking Products CUGs (and vice versa). Atthe Data Networking Products endpoint CUG membership is performed.

A CUG map table contains the Data Networking Products CUG identifier (an 8-bit value) and theICN (32-bit value). The ICN includes a (DNIC or INIC) followed by a 5 digit number. (Refer toRecommendation X.180.)

CUG with Access Indication

The CUG with outgoing access indication is a network utility used for enabling the establishmentof virtual calls by DTEs that are members on international CUGs. This utility is similar to theCUG indication utility except it refers to international CUGs with outgoing access capability.This capability enables the members of the international CUGs to establish virtual calls withnon-members.

Check of Traffic Agreements for Incoming Calls

Check of Traffic Agreements for Incoming Calls and Disallowing of New Calls over a gatewayare non-X.75 network utilities that are supported by international X.75 interworkings, subject tobilateral agreement.

Traffic agreement checking defines the pattern set (the traffic agreement) used to check incominginternational calls from the originating country. The traffic agreement check is based on theDNIC or the CC of the calling DTE and on the information contained in network routing tables.

Disallowing calls over a gateway module allows the network administrator to disallow furthercalls through the gateway while keeping existing calls in progress. This feature providescapabilities to:

schedule service outages without disrupting active calls

control congestion or traffic patterns

limit access to the node (i.e., security mechanism)

The network administrator can restrict calls in the incoming and/or outgoing direction. The X.25feature provides a similar capability.


Security________________Restricted Access

The remove access command enables the network administrator to restrict access on X.25,X.25P, and X.75 ports. Both the X.25P module and X.75 module allow access to be restricted inthe incoming and/or outgoing direction. The X.25 module allows access to be restricted in theoutgoing direction only.

In addition, the network security mechanisms, such as password security, originating groupsecurity, and call screening, apply to X.75 service.


The Network Access Control System* augments the basic security functions of the network via asoftware package that runs on a Hewlett-Packard processor. It provides access control, useridentification and authentication, and auditing functions. It authenticates the identity of the userand establishes connections only to destinations permitted for that user. Dial-in modem andterminal users can be provided with a customized menu interface to the network that implementsease of use along with effective security.

The Network Access Control System provides security services for Data Networking Productsnetworks and for LANs. Security for the Data Networking Products environment isaccomplished via the Network Access Controller (NAC), which operates independently, or theRemote Access Controller (RAC), which operates under the control of a Central SecurityAdministration Controller (CSAC). These controllers and the security service sglogin limitaccess to network hosts made available from a Datakit II VCS, BNS-2000 VCS, or BNS-2000network.

Security for the LAN environment is accomplished via TRAC, which is the TCP/IP RemoteAccess Controller, and the security service, Firewall. Firewall protects an internal TCP/IPnetwork from an external TCP/IP network. It allows users from an originating host to connect toa destination host on another TCP/IP network when they authenticate successfully. Gatewayfunctions for TELNET, FTP, and pass-through services are provided.

The Network Access Control System identifies and authenticates each network user, who mustenter a unique identifier (UID) and a personal authenticator. The authenticator can be a passwordor a personal user authentication device. Once a user is authenticated, a connection can be madeonly to destinations for which the user is granted access.

________________

* Release 4.0 provides software upgrades for Network Access Control System users running earlier releases on HP720 and AT&T 3B2 or 6386/33 Model S processors. Release 4.0 is the last release of the Network Access ControlSystem that offers software upgrades on these platforms.


Security________________RemoteNAC

RemoteNAC

NetworkNode

Central SecurityAdministrationController

NetworkNode

NetworkNode

FIGURE 9-8. Security System Configuration with Central Security Administration

Dial-in modem security for the LAN environment is accomplished via TACACS protocol. TheTACACS protocol provides authentication and access control functions for the dial-in LAN users.The TACACS protocol is based on the client/server model where the TACACS client software onthe communication server collects the userid and authenticator and sends the results to theTACACS server on the NAC system. The TACACS server checks the information against thedatabase and sends the results to the client. If the authentication is successful, the client connectsthe user to the communications server. If the user repeatedly fails authentication, the NACdisconnects the call. If the number of failed access attempts reaches a specified threshold, theNAC can suspend the user’s UID temporarily, and notify the security administrator and theStarKeeper II NMS.

Features

The Network Access Control System offers several features that provide flexibility in configuringnetwork security:

two-factor security — Two-factor security can be implemented by requiring the user to have ahand-held authentication device and a personal identification number (PIN). SecurityDynamics SecurID generates a one-time password based on a proprietary synchronized timealgorithm.

security administration control — Security in small networks, which may be handled by asingle stand-alone NAC, can be expanded easily by adding more NACs functioningindependently, or by adding a Central Security Administration Controller (CSAC). Adistributed security system can contain up to 10 Remote NACs under the control of oneCSAC equipped with external disk storage.


Security________________customized system — The Network Access Control System offers the ability to vary thesecurity system configuration and types of authentication to suit the needs of each network. Inaddition, the system features a menu interface with customizable screens for initial message orgreeting to users, user authentication (before or after menu selection), user help information,choice of call destination.

For more information, see the Network Access Control System Administration Guide.

DKAP Security Software

An additional level of security is provided through security programs that run on the DKAPmodule. For example, Call Back Modem (CBM) software consists of a dial-in modem pool, adial-out modem pool, and the DKAP module running CBM software. When a user dials into adestination for which CBM security is defined, the call is routed to the CBM software. The CBMsoftware performs user authentication; if the call passes authentication, it is immediatelydisconnected. Then the CBM software calls the final call destination, calls back the user at anumber stored in its memory, and splices the user to the destination. The following figure showsthe sequence of events. There are at least two advantages to this method:

The user location can be verified because the call is returned to a specific telephone number.The user must be at that location to receive the return call so physical security can bearranged, whereas a call to a dial-in modem can originate almost anywhere.

The final call destination to the host can be hidden from the user, who needs to know onlyenough to connect to the callback modem. The CBM software actually makes the connection.Users having the ability to access multiple hosts can get to the DESTINATION: prompt.

If error conditions occur or the call does not pass authentication, CBM software displays errormessages to the user that can indicate any of the following conditions:

Cannot Connect To Your DestinationThe CBM could not establish a connection to the user destination. Depending on theuser’s entry in the password table, the user is disconnected or reprompted for adestination.

Error Invalid PasswordThe password that the user entered was not found in the password table. If the maximumnumber of attempts (five attempts) are exceeded, the call is terminated. If the maximumnumber of attempts are not exceed, the user is prompted to re-enter the password.

Too Many Invalid AttemptsThe user exceeded the maximum number of attempts to enter a correct password (fiveattempts) or a destination (three attempts). The call is terminated.

TIME OUTThe user did not enter a password within the required period of time. The call isterminated.

For more information about this product, see the Call Back Modem Reference Manual.


Security________________

CBM SOFTWARE CALLS DESTINATION AND USER

1

2

3

4

CallDestination

dial-inmodem

NodeCall

Originator

DKAPUSERAUTHENTICATION

CallDestination

dial-outmodem

NodeCall

Originator

DKAP

CallDestination

NodeCall

Originator

CBM SOFTWARE DISCONNECTS CALL

USER INITIATES CALL

CBM SOFTWARE SPLICES CALL TO DESTINATION

FIGURE 9-9. Call Back Modem Security


Security________________Network Security and LAN Interconnection

A Data Networking Products network imposes security of a different type than the typical LAN.Network security operates in the interval before a call is connected. It governs access toendpoints. Once a connection is made between endpoints, the network has no further securityfunction to perform. From that moment, security depends on the higher level protocol governingthe interface between endpoints. If the session takes place between endpoints on separate LANsegments, the LAN operating system for each endpoint determines the security available. Atypical LAN can impose several types of access controls to files and programs in a server. If thesession is established between an endpoint on a LAN and an endpoint in the WAN, securitydepends on the applications running in both endpoints.

LPM Security

Routing security for the LAN Protocol Module (LPM) is integrated in existing node security thatis based on permanent virtual circuits (PVCs). The LPM implements routing security byproviding a mechanism for configuring port screening filters. These filters control whether thePVCs associated with any two ports on an LPM, whether physical or virtual, can transmit databetween each other.

The network administrator can specify screening lists of LAN physical ports (lanports) and/orvirtual frame relay ports (frports) as an IP routing security measure. The LPM screening listdefines those other ports from which IP traffic cannot be routed for a physical LAN port or avirtual frame relay port. IP traffic originating from the excluded ports is discarded.

Screening lists should be symmetrical to prevent useless one-way transmission of data. Forexample, if frport 2 screens out data from frport 3, then frport 3 should screen out datafrom frport 2.

If a lanport is being entered, the network administrator can specify the following:

The other lanport, which means that any data that would flow from the other lanport throughthe lanport being configured is to be discarded. Only one other lanport can be specified.

The frport, which can be a list specifying any frport value from 1 to 27. Specifying frports inthis list means that any data that would flow from any listed frport through the lanport beingconfigured is to be discarded.

If an frport is being entered, the network administrator can specify the following:

The lanport, which can be a list specifying any lanport value in the range of 1 to 2.Specifying lanports in this list means that any data that would flow from any listed lanportthrough the frport being configured is to be discarded.

The frport, which can be a list of frport values in the range of 1 to 27, excluding the frportnumber currently being entered. Specifying frports in this list means that any data that wouldflow from any listed frport through the frport being configured is to be discarded.


Security________________Default Routing and Security

The default routing feature operates by substituting a default address for the destination address inthe original call request. Thus the call request eventually reaches its destination, but only afterbeing routed through the default address. In the process, it is subjected to security screening asusual. The effect depends on the type of security screening being enforced.

Setting up default routing security requires coordination of the security profiles in several nodes.

Security Planning Examples

This section gives several examples of network security and explains how to apply securityfeatures to support the access needed. The examples include originating group security, CUGsecurity, and call screening security.

Originating Group Security Example

This example shows a network of two nodes, with several terminals connected to two hostcomputers: payroll and billing. In this configuration, two computers (billing and payroll) areconnected to node01, and several terminals are connected to both node01 and node02. Someterminals need to access the billing host computer, and others need to access the payroll hostcomputer.

Overall security requirements include restricting access to each computer so only payrollterminals can access the payroll computer, and only billing users can access the billing computer.In addition, the billing supervisor needs to assume group membership in any billing group.


Security________________

node 01

pay 01

bill 01

bill 02

payroll

billing

node 02

network: usaarea: pa

pay 02

bill 03

bill supv

trunk 1

FIGURE 9-10. Originating Group Security Example

The following table summarizes the access requirements that might be prepared during thesecurity requirements survey for this network.

TABLE 9-2. Originating Group Access Requirements

_ ___________________________________________________Originating Group Name Access Requirement_ ____________________________________________________ ___________________________________________________

pay01 calls payroll

pay02 calls payroll

bill01 calls billing



billsupv selects bill01, bill02, and bill03_ ___________________________________________________


Security________________To meet these requirements, the following addresses and security patterns need to be defined.

1. Administer the following originating groups:_ _____________________________

Endpoint Group Name_ ______________________________ _____________________________Payroll terminals pay01, pay02

Billing terminals bill01, bill02, bill03

Billing supervisor billsupv_ _____________________________

2. Administer the select group for use by billsupv.

3. Administer the following service addresses:_ ____________________________________________

Endpoint Address Type Service Address_ _____________________________________________ ____________________________________________Payroll computer Mnemonic usa/nj/node01/payroll

Billing computer Mnemonic usa/nj/node01/billing_ ____________________________________________

4. From this information, you could derive the following originating group security patterns:_ _____________________________________________________________

Service Address Security Pattern Effect_ ______________________________________________________________ _____________________________________________________________payroll */*/pay[0-9][0-9] Allows access to all originating groups

named pay00 to pay99 in the usa network.

billing */*/bill0[1-3] Allows access to bill01, bill02, and

bill03 only._ _____________________________________________________________

Note that billsupv does not have access to the billing computer. To call the billing computer,billsupv must use the select group command to assume group membership in one of thethree groups that are allowed access.


Security________________CUG Security Example

This example shows a network containing a node that connects to an X.25 host through a 5ESSSwitch, and is connected directly to another X.25 host. Both hosts are members of separateCUGs. Several terminals make switched calls to each host. In addition, the directly attached X.25host accepts calls from the open part of the network.

0002 0003EPN0001

Closed user group 02

Closed user group 01

switch5ESS

0100-800-555-2345

X.25host

node 01

term 02

term 01

X.25host

00060005EPN 0004

0001-900-888-1212

FIGURE 9-11. CUG Security Example


Security________________The following table summarizes the access requirements that might be prepared during thesecurity requirements survey for this network.

TABLE 9-3. CUG Access Requirements

_ _________________________________________Endpoint Access Requirement_ __________________________________________ _________________________________________

EPN 0001–0003 calls 0001-900-888-1212_ _________________________________________EPN 0004–0006 calls 0100-800-555-2345_ _________________________________________term01–term02 calls 0100-800-555-2345_ _________________________________________

0100-800-555-2345 receives calls from EPN0004–0006

term01, term02_ _________________________________________

To meet these requirements, administer the following information in the database. (All specificvalues, such as service addresses, are for this example only.)

1. With enter node, administer the node address as follows:_ ____________

DNIC 0100_ ____________SR 800_ ____________SA 555_ ____________

2. With enter profile, administer the following CUG profiles:_ _________________________________________

Identifier Purpose CUG_ __________________________________________ _________________________________________cugprof1 For PDN gateway 1_ _________________________________________cugprof2 For X.25 host 2_ _________________________________________cugprof3 For endpoints EPN0001–EPN0003 1_ _________________________________________cugprof4 For endpoints EPN0004–EPN0006 2_ _________________________________________


Security________________3. With enter group, administer the following groups:

_ ____________________________________________Type Name Purpose_ _____________________________________________ ____________________________________________

Originating epn123 For endpoints EPN0001–EPN0003

epn456 For endpoints EPN0004–EPN0006

term12 For endpoints term01, term02_ ____________________________________________Receiving pdn01 PDN gateway

x25host1 X.25 host_ ____________________________________________

4. With enter gateway, administer the PDN gateway as follows:_ ____________________________________________________

Parameter Prompt Option_ _____________________________________________________ ____________________________________________________GATEWAY ADDRESS 0001 900 888 0000

GATEWAY PDN PREFIX none

PAD SUPPORT host

LOCAL X.3 PROFILE ID Use the default

REMOTE X.3 PROFILE ID Use the default

REMOTE X.3 PARAMETER SET Use the default

GATEWAY CLOSED USER GROUP PROFILE ID cugprof1

NETWORK CLOSED USER GROUP PROFILE ID cugprof1

GATEWAY ENDPOINT NUMBER OR RANGE 1212

X.121 ADDRESS 0100 800 555 7654_ ____________________________________________________

5. With enter address, define a PAD address for the X.25 host and the PDN gateway:_ __________________________________________________

Address Purpose Originating Group Security Pattern_ ___________________________________________________ __________________________________________________pdnpad PDN gateway epn123_ __________________________________________________hostpad X.25 host epn456,term12_ __________________________________________________

6. With enter ty, administer the terminals for endpoints EPN0001–EPN0006, term01, andterm02.

7. With enter x25, administer the host and PDN modules and ports.


Security________________Trunk Call Screening Example

This example shows the effect of call screening security in a network consisting of node01,node02, and node03. The configuration is similar to the previous originating group example, withthe addition of another node (node03) and an asynchronous terminal (asyncterm) that callsanother host on node01. Trunk call screening provides a simple way to segregate calls for thedestinations on node01. Calls entering node01 from trunk1 are allowed to go only to payroll orbilling. Calls entering node01 from trunk2 are allowed to go only to asynchost.

node 01

pay 01

bill 01

bill 02

payroll

billing

node 02

network: usaarea: pa

pay 02

bill 03

bill supv

trunk 1

node 03

asyncterm

trunk 2

asynchost

FIGURE 9-12. Trunk Call Screening Example


Security________________For this example, in addition to the enter commands to administer the nodes, terminals, andhosts, the following would be required.

1. With enter profile, administer the following options for trunk call screening profiles:_ __________________________

Parameter Prompt Option_ ___________________________ __________________________Profile ID trunk1

Security Pattern !asynchost_ __________________________Profile ID trunk2

Security Pattern asynchost_ __________________________

2. With enter trunk, enter trunk1 to node01 with the following information:___________________________

Parameter Prompt Option______________________________________________________Group trunk1

Call Screening Profile ID trunk1___________________________

Using the trunk1 call screening profile prevents calls entering node01 through trunk1 fromaccessing the service address asynchost.

3. With enter trunk, enter trunk2 to node01 with the following information:___________________________

Parameter Prompt Option______________________________________________________Group trunk2

Call Screening Profile ID trunk2___________________________

Using the trunk2 call screening profile allows calls entering node01 through trunk2 to accessonly the service address asynchost.


________________Database

Basic Structure 10-3

Database and System Limits 10-4Database Resizing 10-7


________________Database

All physical units and logical entities existing in the node and network are defined in a set ofinterconnected tables in the configuration database. Since these tables consist of both fixed andvariable limits, planning might be required.

This chapter provides some guidance on major components of the database, how to determine ifdatabase planning is needed, and the tools and techniques available to assist in this planning.

This chapter does not describe all database tables nor their contents. Detailed instructions forconfiguring different networks is beyond the scope of this document. If database planningassistance is required, the Lucent Technologies National Product Training Center can recommendcourses. Other aspects of database planning are treated elsewhere as follows:

An overview of how the network’s physical units relate to its logical entities is provided in theConnection-Oriented Network Services chapter.

Administration issues regarding node hardware parameters are explained in detail in theNode, Concentrators and Multiplexers, Trunks, and Interface Modules chapters.

Administration issues regarding node software parameters are explained in detail in theAddresses and Groups, Routing, and Security chapters.

The database commands referred to in this chapter, and other database commands that areavailable for network administrator use, are explained in detail in the appropriate NodeReference and the Data Networking Products Commands Reference.

Basic Structure

The database consists of a set of interconnected tables that contain information on each piece ofphysical equipment, each logical entity, and the relationships established between them. Theinformation on the physical entities includes the following:

Physical Node. The database contains information that defines the hardware configuration,including the type and location of critical and redundant equipment along with the numberand type of shelves.

Concentrators or Multiplexers. Each concentrator and multiplexer is independentlyadministered in the database. Associated with each are the following:

— the common equipment configuration

— the number, type, and location of trunk links to the node

— the number, type, location of each interface module in the concentrator or multiplexer


Database________________— the number and type of interface ports on each interface module

Trunk Modules. The type and physical location of all trunk modules are specified, includinginternodal trunks and concentrator/multiplexer links.

Interface Modules. The type and physical location of all interface modules are specified,including the number and type of interface ports used on each module.

Also included are logical entities such as the following:

Addresses. All addresses known to the node are defined, as well as their association to otherphysical and logical entities.

Groups. Each group is defined by name, type, and association with other physical and logicalentities. Certain security parameters are also specified.

Logical Component Parameters. Various parameters are recorded for each module and itscomponents (boards, ports, control units, DLCIs). These parameters define the serviceprovided by the module and its components.

Specialized Service and Security Parameters. Numerous parameters are defined for the typesof profiles, gateways, and SNIs used by certain interface modules. These parameters areapplicable to security methods, PDNs and PSPDNs, and SMDS resources.

Database and System Limits

The configuration database contains both fixed and variable size tables. The dbaudit commandcan be used to determine the maximum limit of each table. These limits should be consideredwhen planning each node. The dbaudit command can be used later to report on the current usageof each database table resource based on the information currently administered in the database.

The level 0 output of dbaudit provides a summary of database table usage by resource. The level1 output of dbaudit provides a more detailed breakdown of the individual database tables.Examples are shown in the following two screens.


Database________________Generating a Level 0 Database Table Usage Report

UTILITY> dbaudit -l0Database Table Usage (version = BN2.F-2, size = 874860)

Resource % Available # Available Misc Information-------- ----------- ----------- ----------------Concentrators 99% 252Modules 99% 575Ports 100% 6395Endpoints 100% 5390PDDs 100% 2000PDD addresses 100% 2500PDD Space 100% 6000Address Names 100% 3000Logoff Strings 100% 50Address Numbers 100% 3500X.25 Gateways 100% 10Gateway Maps 100% 512CUG Profiles 100% 750CUG List Entries 100% 6000Call Scr Profiles 100% 100SP List Entries 100% 1024Pattern Space 100% 27036Rtt Module Entries 100% 50Rtt CS Entries 100% 500Node RT Entries 100% 100Threshold Entries 80% 16SMDS SNI Entries 100% 100SNI IND. Entries 100% 800SNI SCR. Entries 100% 6400SNI GRP. Entries 100% 2400Attributes 100% 2599 Share ratio = 1:1Attribute Space 100% 31992 Largest free blk = 31992Billing Profiles 100% 8CUG Maps 100% 8Groups 100% 4093Host Names 100% 254X.3 Profiles 85% 17Data Strings 100% 65488 Largest free blk = 65488


Database________________Generating a Level 1 Database Table Usage Report

UTILITY> dbaudit -l1Database Table Usage (version = BN2.F-2, size = 874860)

tbl_name %free totcnt free in_use hi_id misc_info--------- ----- ------ ------- ------- ------- --------COMM 99% 254 252 2 1DEVINDEX 97% 4176 4044 5 131 # Reserved = 127DEVCON 99% 580 575 5 128PORTINDEX 100% 9280 9267 5 12 # Reserved = 8PORT 100% 6400 6395 5 4LDEV 100% 5400 5390 10 9PDDTAB 100% 2000 2000 0 -1PADDR 100% 2500 2500 0 -1PADDRSORT 100% 2500 2500 0 -1PDD_STR 100% 6000 6000 0 -1SNAME 100% 3000 3000 0 -1LOGTAB 100% 50 50 0 -1NUMBER 100% 3500 3500 0 -1NUMSORT 100% 3500 3500 0 -1GATEWAY 100% 10 10 0 -1GWSORT 100% 10 10 0 -1GWMAP 100% 512 512 0 -1CPROFILE 100% 750 750 0 -1CUGSORT 100% 750 750 0 -1CUGLIST 100% 6000 6000 0 -1SPROFILE 100% 100 100 0 -1SPSORT 100% 100 100 0 -1SPLIST 100% 1024 1024 0 -1SPSTRING 100% 27036 27036 0 -1RTTMOD 100% 50 50 0 -1RTTLIST 100% 128 128 0 -1RTTCS 100% 500 500 0 -1CSINDEX 100% 3200 3200 0 -1NODERT 100% 100 100 0 -1NRTSORT 100% 100 100 0 -1THSMDS 80% 20 16 4 3THLIST 80% 20 16 4 3SNISMDS 100% 100 100 0 -1SNILIST 100% 508 508 0 -1SNIINDADR 100% 800 800 0 -1SNIINDLIST 100% 800 800 0 -1SNISCRADR 100% 6400 6400 0 -1SNISCRLIST 100% 6400 6400 0 -1


Database________________SNIGRPADR 100% 2400 2400 0 -1SNIGRPLIST 100% 2400 2400 0 -1ATTRINDEX 100% 2600 2599 1 0 Share ratio = 1:1ATTR_MAP 100% 1300 1297 1 1 # Reserved = 2ATTRIBUTES 100% 32000 31992 8 0 Largest free blk = 31992BILLPROF 100% 8 8 0 -1BPSORT 100% 8 8 0 -1CMPROF 100% 8 8 0 -1CMAPSORT 100% 8 8 0 -1CMAPLIST 100% 2040 2040 0 -1GRPHDR 100% 4099 4093 6 6G_NLIST 100% 4100 4094 6 5H_NLIST 100% 254 254 0 -1XPROFILE 85% 20 17 3 2DSTRMAP 100% 2000 1997 1 1 # Reserved = 2DSTRING 100% 65520 65488 32 0 Largest free blk = 65488CC0>

As the node and network are planned, one or more of these tables might reach capacity. Carefulplanning can usually avoid this problem. As names, addresses, security patterns, and commentsare planned, remember that short patterns or strings use less space and lessen the possibility ofdepleting database resources.

Careful planning helps to conserve database resources; but if database resources are depleted,consider using the following space-saving measures:

Resize the database using dbresize.

Consolidate groups, service addresses, and security patterns.

Delete unused modules and ports.

Reduce the number of predefined destinations (PDDs).

Restructure network nodes to use default routing.

Database Resizing

The dbresize command is used to change the sizes of database tables. Unused space in one areais reallocated to another that needs additional resources; the number and size of database tables isautomatically adjusted based on current usage. If the new table sizes do not meet network needs,the administrator can reject the new table sizes. In addition, the administrator can also back outof the resizing operation.

This command produces a report showing the old table sizes and new table sizes. The changesmade do not take effect until the node is rebooted.


________________Appendix A. Recommended

Spare Parts

This appendix provides the quantity of spare parts recommended for the following equipment andfor the trunk and interface modules residing in this equipment:

Series M2 Shelf

Series M1 Shelf

Multipurpose Concentrator (BNS-2000 MPC)

Base Power Unit

SAM16

SAM64

SAM504

For spare parts information for other equipment (such as bridges and routers), refer to thedocumentation for the particular piece of equipment.

Sparing Quantities

The sparing quantities shown are based on the number of modules in service for each location.For redundant equipment, count each module separately to determine the number of modules inservice. For example, a redundant Switch module counts as two Switch modules in service. Donot count backup modules as spares.

The values shown are recommendations only. The quantity of spares can be reduced whenseveral nodes are centrally supported.

Parts are listed in alphanumeric order according to the part code in the left column.

Data Networking Products Planning Guide, Issue 4 A-1

Appendix A. Recommended Spare Parts________________TABLE A-1. Series M2 Shelf Common and Critical Modules

_ ____________________________________________________________________________Sparing quantity (based on

total number of parts in service)_ ____________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________CMA1 Switch module board 1 3 4 5 5_ ____________________________________________________________________________CMA2 CIM board 1 3 4 5 5_ ____________________________________________________________________________CMC2 CIM I/O board 1 2 3 3 3_ ____________________________________________________________________________CMC3 Status and Stratum 4 I/O board 1 2 3 3 3_ ____________________________________________________________________________CNA1 Inter-switch I/O board 1 3 4 5 5_ ____________________________________________________________________________CNA2 Extension I/O board 1 3 4 5 5_ ____________________________________________________________________________CNA7 Extended Cable/Clock & RIB Status I/O board 1 3 4 5 5_ ____________________________________________________________________________CNA8 Enhanced Extension Shelf Cable Clock I/O board 1 2 3 3 3_ ____________________________________________________________________________CTG13 Extended Switch Module 1 3 4 5 5_ ____________________________________________________________________________CUW1 RIB 1 2 3 3 3_ ____________________________________________________________________________

TABLE A-2. Series M2 Shelf Miscellaneous Spares


total number of parts in service)_ __________________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________405753187 Fan 1 1 2 2 2_ ____________________________________________________________________________406063941 15A shelf fuse 4 8 32 64 64

Littlefuse #257015

_ ____________________________________________________________________________406733485 Air Filter #UAF261 2 for each unit in service_ ____________________________________________________________________________ACX582 Bikor AC power unit 1 2 2 3 3_ ____________________________________________________________________________CRF1 Fan filter circuit pack 1 1 2 2 2_ ____________________________________________________________________________DCX1836 Bikor DC power unit 1 2 2 3 3_ ____________________________________________________________________________ED3P302-30,G4 AC Power module assembly 1 1 2 2 2_ ____________________________________________________________________________ED3P302-30,G6 DC Power module assembly 1 1 2 2 2_ ____________________________________________________________________________

A-2 Data Networking Products Planning Guide, Issue 4

Appendix A. Recommended Spare Parts________________TABLE A-3. Series M1 Shelf Common and Critical Modules


total number of parts in service)_ __________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________611C or ACX582 OLS (AC) power unit 1 2 2 3 3_ ____________________________________________________________________________ASP1 Clock/Repeater 1 1 2 2 2_ ____________________________________________________________________________ASP2 Fuse board circuit pack 2 2 4 4 4_ ____________________________________________________________________________ASP4B SCSI/DKI I/O board (ECPU) 1 1 2 2 2_ ____________________________________________________________________________ASP7B CTRM I/O board 1 1 2 2 2_ ____________________________________________________________________________ASP8 Tape (Internal) I/O board (ECPU) 1 1 2 2 2_ ____________________________________________________________________________AWJ12 Disk I/O board (ECPU) 1 1 2 2 2_ ____________________________________________________________________________AWJ15 ECPU I/O board (ECPU) 1 2 3 3 3_ ____________________________________________________________________________AWJ16B MRCM I/O board (ECPU) 1 1 2 2 2_ ____________________________________________________________________________CSD9 Tape (Internal) I/O board (CCM) 1 1 2 2 2_ ____________________________________________________________________________CTS1 MRCIO I/O board (CCM) 1 2 3 3 3_ ____________________________________________________________________________CTS2 Simplex I/O board (CCM) 1 2 3 3 3_ ____________________________________________________________________________DCX1836 OBS (DC) power unit 1 2 2 3 3_ ____________________________________________________________________________ED3P325-30,G407 Tape (external) (CCM) 1 2 3 3 3_ ____________________________________________________________________________ED5P056-30,G2 Connector assembly (bus terminator) 1 1 2 2 2

Series M1 Shelf_ ____________________________________________________________________________MC1D138A1 ECPU module board (ECPU) 1 3 5 5 5_ ____________________________________________________________________________TN1001B Clock module board 1 2 3 3 3_ ____________________________________________________________________________TN1003 Repeater module board 1 2 3 4 4_ ____________________________________________________________________________TN2096 CTRM module board 1 2 3 3 3_ ____________________________________________________________________________TN2097 SCSI tape (40 MB) module board (ECPU) 1 2 3 3 3_ ____________________________________________________________________________TN2099 Switch module board 1 2 3 3 3_ ____________________________________________________________________________TN2109B/C MRCM module board (ECPU) 1 2 3 3 3_ ____________________________________________________________________________TN2175B DISK drive (high capacity) (ECPU) 1 2 3 3 3_ ____________________________________________________________________________TN2233 Tape (internal) (CCM) 1 2 3 3 3_ ____________________________________________________________________________TN2235 CCM module board (CCM) 1 3 5 5 5_ ____________________________________________________________________________UN635B SCSI/DKI (ECPU) 1 2 3 3 3_ ____________________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-4. Series M1 Shelf Miscellaneous Spares

_ _______________________________________________________________Sparing quantity (based on

total number of parts in service)_ _________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ ________________________________________________________________ _______________________________________________________________405725433 7.5 AMP fuse 4 8 32 64 64_ _______________________________________________________________405753187 Fan 1

1

2

2

2_ _______________________________________________________________406177766 Tape cassette 3 per database_ _______________________________________________________________846401768 MRCM A0 cable 1 1 2 2 2_ _______________________________________________________________846401784 MRCM B0 cable 1 1 2 2 2_ _______________________________________________________________846401792 MRCM B1 cable 1 1 2 2 2_ _______________________________________________________________846401818 MRCM S cable 1 1 2 2 2_ _______________________________________________________________846401826 MRCM R0 cable 1 1 2 2 2_ _______________________________________________________________846401834 MRCM R1 cable 1 1 2 2 2_ _______________________________________________________________847671773 AB, CCM cable 1 1 2 2 2_ _______________________________________________________________847671781 ABM, CCM cable 1 1 2 2 2_ _______________________________________________________________847671799 SCSI-75, CCM cable 1 1 2 2 2_ _______________________________________________________________847671807 A1B1C1, CCM cable 1 1 2 2 2_ _______________________________________________________________847671815 PWR-MOL, CCM cable 1 1 2 2 2_ _______________________________________________________________847671823 PWR-MOL-S, CCM cable 1 1 2 2 2_ _______________________________________________________________847671831 SCSI-79, CCM cable 1 1 2 2 2_ _______________________________________________________________847671849 SCSI-79-S, CCM cable 1 1 2 2 2_ _______________________________________________________________847671856 SCSI-75-S, CCM cable 1 1 2 2 2_ _______________________________________________________________847671864 ITAPE, CCM cable 1 1 2 2 2_ _______________________________________________________________847671872 ITAPE-S, CCM cable 1 1 2 2 2_ _______________________________________________________________847671880 XTAPE, CCM cable 1 1 2 2 2_ _______________________________________________________________847671898 A1B1C1-S, CCM cable 1 1 2 2 2_ _______________________________________________________________ACX582 Bikor AC power unit 1 2 2 3 3_ _______________________________________________________________ASP2 Fuse board 2 2 4 4 4_ _______________________________________________________________DCX1836 Bikor DC power unit 1 2 2 3 3_ _______________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-5. Series M1 Shelf Miscellaneous Spares

_ _______________________________________________________________________Sparing quantity (based on


Code Description

3 10 30 100 100_ ________________________________________________________________________ _______________________________________________________________________ED2P501-30,G9 Standard bus cable 1 1 2 2 2_ _______________________________________________________________________ED2P501-30,G10 Extended bus cable 1 1 2 2 2_ _______________________________________________________________________ED2P501-30,G11 Standard Clock cable 1 1 2 2 2_ _______________________________________________________________________ED2P501-30,G12 Extended Clock cable 1 1 2 2 2_ _______________________________________________________________________ED2P501-30,G13 Ground cable (CO frame) 1 1 2 2 2_ _______________________________________________________________________ED3P302-30,G5 Power module assembly; ACD 1 1 2 2 2_ _______________________________________________________________________ED3P302-30,G7 Power module assembly; DCD 1 1 2 2 2_ _______________________________________________________________________ED3P324-30,G16 MRCM power cable 1 1 2 2 2_ _______________________________________________________________________ED5P063-30,G1 Interface Repeater Unit (IRU) 1 2 3 4 5_ _______________________________________________________________________ED5P100-30,G133 Alarm Relay Unit 5 VDC 1 2 3 3 3_ _______________________________________________________________________FL2P-P CIM-CTRM fiber optic cable 1 1 2 2 2_ _______________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-6. BNS-2000 MPC Common and Critical Modules and Miscellaneous Parts


total number of parts in service)_ _____________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________405725433 7.5 AMP fuse 4 8 32 64 64_ ____________________________________________________________________________405753187 Fan 1 1 2 2 2_ ____________________________________________________________________________611C or ACX582 OLS (AC) power unit 1 2 2 3 3_ ____________________________________________________________________________ACX582 Bikor AC power unit 1 2 2 3 3_ ____________________________________________________________________________ASP1 Clock/Repeater I/O board 1 1 2 2 3_ ____________________________________________________________________________ASP2 Fuse board 2 2 4 4 4_ ____________________________________________________________________________DCX1836 Bikor (OBS) DC power unit 1 2 2 3 3_ ____________________________________________________________________________ED2P501-30,G9 Standard bus cable 1 1 2 2 2_ ____________________________________________________________________________ED2P501-30,G10 Extended bus cable 1 1 2 2 2_ ____________________________________________________________________________ED2P501-30,G11 Standard Clock cable 1 1 2 2 2_ ____________________________________________________________________________ED2P501-30,G12 Extended Clock cable 1 1 2 2 2_ ____________________________________________________________________________ED2P501-30,G13 Ground cable (CO frame) 1 1 2 2 2_ ____________________________________________________________________________ED3P302-30,G1 Power module assembly for AC distr. 1 1 2 2 2_ ____________________________________________________________________________ED5P056-30,G2 Connector assembly (bus terminator) 1 1 2 2 2_ ____________________________________________________________________________ED5P063-30,G1 Interface Repeater Unit (IRU) 1 2 3 4 5_ ____________________________________________________________________________TN1001B Clock module board 1 2 3 3 3_ ____________________________________________________________________________TN1002B Switch module board 1 2 3 3 3_ ____________________________________________________________________________

TABLE A-7. Base Power Unit Spares


total number of parts in service)_ _____________________________________________1 4 11 31to to to to Over

Code Description

3

10

30

100

100_ _____________________________________________________________________________ ____________________________________________________________________________405769704 Air filter; modular cabinet 2 for each unit in service_ ____________________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-8. SAM16 Spares



Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________406703389 Fan 1 2 3 3 3_ ____________________________________________________________________________406744557 Air Filter 2 4 6 8 10_ ____________________________________________________________________________106670151 CRA1 (V.35) Module 1 1 2 2 3_ ____________________________________________________________________________106670169 CRA2 (RS-232) Module 1 1 2 2 3_ ____________________________________________________________________________901231316 Fuse 5 x 20 mm, 2A 5 10 10 15 15_ ____________________________________________________________________________901231324 Fuse 5 x 20 mm, 1A 5 10 10 15 15_ ____________________________________________________________________________CPY1 SAM16 Circuit Pack 1 1 2 2 3_ ____________________________________________________________________________

TABLE A-9. SAM64 Spares


total number of parts in service)_ ______________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________405718602 Fan for J1P070V-1 1 2 3 3 3_ ____________________________________________________________________________405753187 Fan for J1P186J-1 2 4 6 8 10_ ____________________________________________________________________________406426569 Circuit breaker for J1P186J-1 1 2 3 4 5_ ____________________________________________________________________________997942305 Fuse for J1P070V-1 5 10 10 15 15_ ____________________________________________________________________________ED2P466-30,G1 TERM32 (SAM64, SAM504) 1 1 2 2 2_ ____________________________________________________________________________ED2P491-30,G(11) Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED5P055-31,G(219) SAMDL I/O cable 1 1 2 2 2_ ____________________________________________________________________________TN1394C TCON board 1 2 3 3 3_ ____________________________________________________________________________TN1395 Power board for J1P070V-1 1

2

3

3

3_ ____________________________________________________________________________TN2166 AC power board for J1P186J-1 1 for every 5 power units in service._ ____________________________________________________________________________TN2167 DC power board for J1P186J-1 1 for every 5 power units in service._ ____________________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-10. SAM504 Spares


total number of parts in service)_ ___________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________405372970 3.5A fuse 10 10 10 20 20_ ____________________________________________________________________________405372988 12A fuse 10 10 10 20 20_ ____________________________________________________________________________405372996 3A fuse 10 10 10 20 20_ ____________________________________________________________________________405373002 0.18A fuse 10 10 10 20 20_ ____________________________________________________________________________405713165 Fan 1 2 2 2 2_ ____________________________________________________________________________410AA Converter module -5 volts 1 2 2 2 2_ ____________________________________________________________________________494MA Converter module ±12 volts 1 2 2 2 2_ ____________________________________________________________________________ED2P462-30,G1 Alarm board 0 0 1 1 2_ ____________________________________________________________________________ED2P466-30,G1 TERM32 (SAM64, SAM504) 1 1 2 2 2_ ____________________________________________________________________________ED2P467-30,G1 Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED2P467-30,G3 Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED2P467-30,G4 Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED2P467-30,G5 Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED2P467-30,G6 Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED2P467-30,G7 Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED2P467-30,G8 Cable assembly 1 1 2 2 2_ ____________________________________________________________________________ED5P100-31,G9 Power Conversion Unit (110 VAC to -48 VDC) 1 1 1 2 2_ ____________________________________________________________________________ED5P100-31,G10 Power Conversion Unit (230 VAC to -48 VDC) 1 1 1 2 2_ ____________________________________________________________________________TN1394C TCON board 1 2 3 3 3_ ____________________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-11. Trunk Module Board Spares



Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________CMA9 Trunk-T3 1 3 4 5 5_ ____________________________________________________________________________CMA9B Trunk-E3 1 3 4 5 5_ ____________________________________________________________________________CMA13 Trunk-E3S, Trunk-T3S 1 3 4 5 5_ ____________________________________________________________________________CMA14 Trunk-T3I (egress) 1 3 4 5 5_ ____________________________________________________________________________CMA16 Trunk-T3I (ingress) 1 3 4 5 5_ ____________________________________________________________________________CMA18 Trunk-T3A/E3A 1 3 4 5 5_ ____________________________________________________________________________MC1D085A1 SFT 1 2 3 4 5_ ____________________________________________________________________________MC1D090A1B SAMSL 1 1 2 2 2_ ____________________________________________________________________________MC1D091A1 SAMML 1 1 2 2 3_ ____________________________________________________________________________MC1D105A1 Trunk-64 1 2 3 4 5_ ____________________________________________________________________________MC1D106A1 SAMDL 1 1 2 2 2_ ____________________________________________________________________________MC1D142A1 SAMSL-N 1 2 3 4 5_ ____________________________________________________________________________MC1D152A1 Trunk-PQ 1 2 3 4 5_ ____________________________________________________________________________TN1391 HS-Trunk 1 1 2 2 2_ ____________________________________________________________________________TN1392 T1-Trunk 1 1 2 2 2_ ____________________________________________________________________________TN1010 Trunk-HS 1 1 2 2 3_ ____________________________________________________________________________TN1015 Trunk-T1 1 1 2 2 2_ ____________________________________________________________________________TN2092B SWT 1 2 3 4 5_ ____________________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-12. Trunk I/O Distribution Board Spares


total number of parts in service)_ ________________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________AWJ2 Trunk-HS 1 1 2 2 2_ ____________________________________________________________________________AWJ3 SFT 1 2 3 4 5_ ____________________________________________________________________________AWJ4 Trunk-T1 1 1 2 2 2_ ____________________________________________________________________________AWJ9 SAMML, SWT 1 1 2 2 2_ ____________________________________________________________________________AWJ10 SWT 1 1 2 2 2_ ____________________________________________________________________________AWJ11 SAMML-N, SWT 1 1 2 2 2_ ____________________________________________________________________________AWJ17 SAMML 1 1 2 2 2_ ____________________________________________________________________________AWJ24 Trunk-PQ 1 1 2 2 2_ ____________________________________________________________________________AWJ33 SWT (G.703) 1 1 2 2 2_ ____________________________________________________________________________CEY1 HS-Trunk (SAM64) 1 1 2 2 2_ ____________________________________________________________________________CEY2 SAMSL (SAM64; V.35) 1 1 2 2 2_ ____________________________________________________________________________CEY3 SAMSL (SAM64; RS-232 DTE) 1 1 2 2 2_ ____________________________________________________________________________CEY4 SAMDL (SAM64) 1 1 2 2 2_ ____________________________________________________________________________CMC6 Trunk-T3, Trunk-T3S 1 3 4 5 5_ ____________________________________________________________________________CMC6B Trunk-T3I, Trunk-T3S 1 3 4 5 5_ ____________________________________________________________________________CMC13 Trunk-E3, Trunk-E3S 1 3 4 5 5_ ____________________________________________________________________________CMC13B Trunk-E3S 1 3 4 5 5_ ____________________________________________________________________________CMC14 Trunk-T3I 1 3 4 5 5_ ____________________________________________________________________________CMC15 Trunk-T3A 1 3 4 5 5_ ____________________________________________________________________________CMC16 Trunk-E3A 1 3 4 5 5_ ____________________________________________________________________________EAA2 SAMSL 1 1 2 2 2_ ____________________________________________________________________________ED2P471-30,G1 HS-Trunk (SAM504) 1 1 2 2 2_ ____________________________________________________________________________ED2P465-30,G1 T1-Trunk (SAM504) 1 1 2 2 2_ ____________________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-13. Interface Module Board Spares


total number of parts in service)_ _________________________________________1 4 11 31to to to to Over

Code Description

3 10 30 100 100_ _____________________________________________________________________________ ____________________________________________________________________________CMA5 AI-E1, AI-T1 1 3 4 5 5_ ____________________________________________________________________________CMA11B AI-E3, AI-T3 1 3 4 5 5_ ____________________________________________________________________________CMA15 GAR 1 3 4 5 5_ ____________________________________________________________________________CMA17 AI-T3P 1 3 4 5 5_ ____________________________________________________________________________CTG1 FRM-M2 1 2 3 4 5_ ____________________________________________________________________________MC1D088A1 TSM8 1 1 2 2 3_ ____________________________________________________________________________MC1D089A1 SYNC8 1 1 2 2 3_ ____________________________________________________________________________MC1D143A1 FRM 1 1 2 2 3_ ____________________________________________________________________________MC1D149A1 TSM-T1 1 1 2 2 3_ ____________________________________________________________________________MC1D151A1 X.75 1 1 2 2 3_ ____________________________________________________________________________MC1D153A1 X.25P 1 1 2 2 3_ ____________________________________________________________________________MC2PO23A1 DKAP 1 2 3 4 4_ ____________________________________________________________________________MC5PO25A1 SLM 1 1 2 2 2_ ____________________________________________________________________________TN1009 CPM-HS 1 2 3 4 5_ ____________________________________________________________________________TN1012 E2A 1 1 2 2 3_ ____________________________________________________________________________TN2094 X.25 1 2 3 4 5_ ____________________________________________________________________________TN2111B MSM 1 2 3 4 5_ ____________________________________________________________________________TN2157 TY12 1 2 3 4 5_ ____________________________________________________________________________TN2229 LPM 1 2 2 2 3_ ____________________________________________________________________________UN211 SLM 1 1 2 2 2_ ____________________________________________________________________________UN315 TERM32 (SAM64 & SAM504) 1 1 2 3 3_ ____________________________________________________________________________


Appendix A. Recommended Spare Parts________________TABLE A-14. Interface I/O Distribution Board Spares

_ _________________________________________________________________________Sparing quantity (based on


Code Description

3 10 30 100 100_ __________________________________________________________________________ _________________________________________________________________________AWJ2 CPM-HS 1 1 2 2 2_ _________________________________________________________________________AWJ4 TY12, MSM 1 1 2 2 2_ _________________________________________________________________________AWJ5 SYNC8, TSM8, X.25 (DCE/DTE) 1 1 2 2 2_ _________________________________________________________________________AWJ6 SYNC8, TSM8, X.25 (DTE) 1 1 2 2 2_ _________________________________________________________________________AWJ7 TSM8, X.25 (NRZI/DTE) 1 1 2 2 2_ _________________________________________________________________________AWJ8 TSM8, X.25 (NRZI/DCE) 1 1 2 2 2_ _________________________________________________________________________AWJ17 SYNC8, TSM8, X.25 (DTE) 1 1 2 2 2_ _________________________________________________________________________AWJ18 SYNC8, TSM8, X.25 (DCE) 1 1 2 2 2_ _________________________________________________________________________AWJ24 FRM, TSM-T1, X.25P, X.75 (DTE) 1 1 2 2 2_ _________________________________________________________________________CMC5 AI-T1 1 3 4 5 5_ _________________________________________________________________________CMC6 AI-T3 1 3 4 5 5_ _________________________________________________________________________CMC6B AI-T3P 1 3 4 5 5_ _________________________________________________________________________CMC8 AI-E1 1 3 4 5 5_ _________________________________________________________________________CMC13 AI-E3 1 3 4 5 5_ _________________________________________________________________________CMC14 AI-T3P, GAR 1 3 4 5 5_ _________________________________________________________________________CMC18 FRM-M2 (ChE1, 75 ohm) 1 1 2 2 3_ _________________________________________________________________________CMC19 FRM-M2 (ChE1, 120 ohm) 1 1 2 2 3_ _________________________________________________________________________CMC20 FRM-M2 (ChT1) 1 1 2 2 3_ _________________________________________________________________________CSD1 FRM (ChT1) 1 1 2 2 3_ _________________________________________________________________________CSD2 FRM (ChE1) 1 1 2 2 3_ _________________________________________________________________________CSD3 FRM (ChE1) 1 1 2 2 3_ _________________________________________________________________________CSD4 X.25P 1 1 2 2 3_ _________________________________________________________________________CSD6 LPM 1 1 2 2 2_ _________________________________________________________________________ED5P074-30,G1 E2A 4 RS-232-C DTE 1 1 2 2 2_ _________________________________________________________________________ED5P077-30,G1 SLM 4 RS-232-C DTE 1 1 2 2 2_ _________________________________________________________________________ED5P080-30,G1 SLM 2 RS-232-C 1 1 2 2 2_ _________________________________________________________________________


________________Appendix B. Database Design

Forms

This section contains sample forms to be used when designing or adding to a database.

Form Title

B-1 User Access Questionnaires

B-2 Database Relationships

B-3 Security Relationships—Originating Group

B-4 Security Relationships—Closed User Group

B-5 Security Relationships—Call Screening

Data Networking Products Planning Guide, Issue 4 B-1

Appendix B. Database Design Forms________________FORM B-1. User Access Questionnaire

____________________________________________________________________________

OFFICE USEONLY

____________________________________________________________________________PORT SERVICE HOST USER

OR USER DEV TYPE ACCESS SPECIALGRP MOD CHN GRP TYPE AS/S/SW* PERMISSION FUNCTION COMMENTS____________________________________________________________________________

____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

________________

*AS = asynchronousS = synchronousSW = switched BISYNC

B-2 Data Networking Products Planning Guide, Issue 4

Appendix B. Database Design Forms________________FORM B-2. Database Relationships

AREA CODE ________ HOST

ORIG EXCH ____________ REC LOCAL

GRP MOD TYPE NODE ____________ MOD TYPE GRP SVC

DEV NAME (PDD) MOD/CHN MOD/CHN NAME ADDRSERVICE ADDRESS_ ______________________

_ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________ _ _________________________________ ________________________________________________________________________________________


Appendix B. Database Design Forms________________FORM B-3. Security Relationships—Originating Group

_ _______________________________________________________________________________

ORIGINATINGSERVICE GROUP NAME SPEEDCALLADDRESS LEVEL SECURITY PATTERN RECEIVE GROUP(S) DIAL STRING

_ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ _______________________________________________________________________________


Appendix B. Database Design Forms________________FORM B-4. Security Relationships—Closed User Group

_ _____________________________________________________________________________

CLOSED OUT IN CALLSERVICE SECURITY USER PREF ACCESS ACCESS SCREENADDRESS PATTERN GROUP IDs CUG Y/N Y/N Y/N

_ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ ______________________________________________________________________________ _____________________________________________________________________________


Appendix B. Database Design Forms________________FORM B-5. Security Relationships—Call Screening

_ ___________________________________________________________

CALL SCREENPROFILE ID SECURITY PATTERN MODULE ADDRESS

_ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ____________________________________________________________ ___________________________________________________________


________________Index

? (directory assistance), 7-11

AAccess,

delay to port, 5-75

end user, 7-17

incoming/outgoing permission, 9-18

to nodes and destination addresses, 7-7

unauthorized, 9-3

Access device(s), 5-37

Access Interface (AI) module(s), 5-3, 5-15. See Also

Group Address Resolver (GAR) module

AI-E1, 5-4, 5-7, 5-10, 5-105, 5-108, A-11, A-12

AI-E3, 5-4, 5-7, 5-10, 5-105, 5-108, A-11, A-12

AI-T1, 5-4, 5-7, 5-10, 5-105, 5-108, A-11, A-12

AI-T3, 5-4, 5-7, 5-10, 5-105, 5-108, A-11, A-12

AI-T3P, 2-32, 5-4, 5-7, 5-10, 5-105, 5-108, A-11,

A-12

Billdats Network Server and, 7-18

Address(es/ing), 5-34

? (directory assistance), 7-11

administrable ranges, 7-15

aliases, 1-12, 7-4, 7-8, 7-9, 7-18

area level, 7-5, 7-8

billing, 1-12, 7-4

combination (service and physical), 7-15–7-16

concentrators and, 7-15

Data Network Identification Code (DNIC), 5-21, 7-5,

7-7, 7-10, 7-11, 7-12, 7-13, 7-14

database and, 10-4

destination, 7-7

directory assistance, 1-12, 7-4, 7-9, 7-11

end user, 7-10–7-11

endpoint number (EPN), 7-5, 7-6, 7-8, 7-10, 7-11,

7-13

exchange level, 7-5, 7-8

formats, 5-21, 5-51, 7-5

Internet Protocol (IP), 5-55

levels, 7-5, 7-7–7-8, 9-9

local level, 7-5

mnemonic, 5-21, 7-4, 7-5, 7-8, 7-19

naming convention, 7-8

network level, 7-5

numeric, 7-4, 7-7, 7-8

physical, 7-3, 7-14, 7-15

planning, 1-12

prefixes, 7-5

restrictions, 5-56, 7-8

service, 7-3, 7-8, 7-12, 9-8

Service Area (SA), 7-5, 7-8, 7-10, 7-11

service level, 7-10

Service Region (SR), 7-5, 7-8, 7-10, 7-11

special, 1-12, 7-4, 7-9

special handling (sphaddr), 7-6, 7-12

speedcalls, 1-12, 7-4, 7-8, 7-9

X.121 E.164 Numbering Plan, 7-4, 7-5, 7-12, 7-13,

7-14

X.121 International Numbering Plan, 7-4, 7-5, 7-12,

7-13

X.121 North American Numbering Plan (NANP),

5-21, 7-4, 7-5, 7-6, 7-12

Air circulation, 2-36, 3-16

AIs. See Access Interface (AI) module(s)

Alarm Relay Unit (ARU), 2-19, 2-23, 3-8, A-5

Aliases, 1-12, 7-4, 7-8, 7-9, 7-18

Alternate routing. See Routing

American National Standards Institute (ANSI),

T1.606, 5-40

Applications processing via customer programmable

module (DKAP), 1-13, 3-4, 3-5, 5-4, 5-6,

5-10, 5-20, 5-103, 5-104, 5-106, 5-107,

5-108, 9-6, 9-24–9-25, A-11

Architecture,

bus, 2-5, 2-6, 2-7

star, 1-7, 2-8, 2-9, 2-10

ARU. See Alarm Relay Unit (ARU)

Asynchronous transfer mode (ATM) switch, 4-11

Data Networking Products Planning Guide, Issue 4 I-1

Index________________ATM. See Asynchronous transfer mode (ATM) switch

ATM Adaptation Layer (AAL5), 5-34, 5-35, 5-43

Autobaud,

CPY1 and, 5-19

Multispeed Module (MSM) and, 5-57

Availability. See Redundancy

BBackplane of the node 2-6, 2-7, 2-8, 2-25, 2-31, 2-32,

5-53, 5-75, 5-78

Backup equipment/modules. See Redundancy

Backward explicit congestion notification (BECN),

5-23, 5-36, 5-37

Bandwidth, 2-3, 2-5, 2-32, 4-14, 5-13, 5-14, 5-29, 5-44,

5-80, 5-96, 8-13

Base Power Unit, 1-6, 2-18, 2-19, 2-23, 2-33, 2-34,

2-37, 2-38, 2-40, 2-43, 2-44, 2-45, 2-46, 3-8,

3-13, 3-16, 3-17, 3-18, A-1, A-6

Battery Distribution Fuse Board (BDFB), 2-50

Bc. See Committed burst (Bc)

Be. See Excess burst (Be)

BECN. See Backward explicit congestion notification

(BECN)

Billdats Network Server, 7-18

Billing,

address for, 1-12, 7-4, 7-9, 7-18

alias and, 7-9

cold standby link and, 3-7

reports, 3-7

Binary Synchronous Communications (BSC), 5-9, 5-58

BNS-1000 interworking, 1-4, 1-15, 4-7, 4-13, 8-17

BNS-2000 interworking, 1-4, 1-5, 1-15, 4-4, 4-7, 4-13,

4-15, 8-17, 8-18

BNS-2000 Multipurpose Concentrator (MPC), 1-7

BNS-2000 VCS interworking, 1-4, 1-5, 4-4, 4-13, 8-17,

8-18,

Broadcast, 5-66, 5-72

BSC. See Binary Synchronous Communications (BSC)

BSC (bisynchronous) protocol, 1-10

bsc3270. See Synchronous 8-port (SYNC8) module

(bsc3270)

Buffer flushing, 5-70, 5-71

Buffer overflow,

CPY1 and, 5-19


TERM32 and, 5-60

Transparent Synchronous Module 8-port (TSM8) and,

5-61

Buildout value, 4-13

Burroughs/NCR Poll/Select protocol, 1-10, 5-9

Bus architecture. See Architecture

CCabinet Interface Module (CIM), 2-11, 2-24, 2-28,

2-36, 2-49, A-2, A-5

Cabinet(s). See Also Modular cabinet(s); Series M1

Shelf; Series M2 Shelf

safety and, 2-38, 3-17

Call Back Modem (CBM) security software, 9-24–9-25

Call screening security, 9-11–9-13

Call(s),

destination, 9-8

dropping, 4-16

groups and, 9-8

looping, 8-16, 8-17

originating endpoints, 2-32

routing, 7-12, 7-13

terminating endpoints, 2-32

CBM. See Call Back Modem (CBM) security software

CC. See Country Code (CC)

CCM. See Control Computer Module (CCM)

Central office (CO), 2-19, 2-23, 3-8

alarm panel, 2-51

equipment configuration with VDM cabinets, 3-22

floor plan, 2-49, 2-50

frame, 1-6, 2-19, 2-33, 2-34, 2-37, 2-38, 2-48, 2-49,

2-51

fuse panel, 2-51

power distribution sources, 2-50

site preparation, 2-39, 2-49, 3-17

structural specifications of frame, 3-9

Central office local area network (CO-LAN),

group and, 7-17

CEY boards [Synchronous/Asynchronous Multiplexer

64-port (SAM64)], A-10

Channel,

administration differences by type, 4-16

group, 7-16

originating group and, 7-17

receiving group, 7-17

I-2 Data Networking Products Planning Guide, Issue 4

Index________________signaling, 4-16

user, 4-16

Channelized E1/T1 (ChE1/ChT1), 5-34, 5-35

CIM. See Cabinet Interface Module (CIM)

CIR. See Committed information rate (CIR)

Clear to send (CTS), 5-13

CLNS. See Connectionless network service (CLNS)

Clock module, 2-6, 2-19, 2-26, 2-36, 3-5, 3-10, 3-15,

A-3, A-6

Clocking, and amount of data, 5-75

Clock/Trunk/Repeater Module (CTRM), 2-11, 2-24,

2-29, 2-30, 2-36, 2-49, 3-5, A-3, A-5

Closed user group (CUG),

identifier, 9-18

incoming access, 9-16

outgoing access, 9-17, 9-18

preferential, 9-18

profile, 9-17, 9-18

security, 9-6, 9-14, 9-16

selection, 9-19

Cluster controller, 5-71

CMA1 Switch module, 2-24, 2-28, 2-35, 2-36, A-2

CMA2 Cabinet Interface Module (CIM), 2-36, A-2

CMC2 Cabinet Interface Module (CIM), 2-36, A-2

CMC3 Stratum 4 Clock (SSM4), 2-28, 2-35, 2-36, A-2

CNA1 Interswitch I/O board, 2-24, 2-28, 2-35, 2-36,

A-2

CNA2 Extension I/O board, 2-28, 2-36, A-2

CNA7 Extended Cable/Clock and RIB Status I/O

board, 2-24, 2-28, 2-35, 2-36, A-2

CNA8 Enhanced Extension Shelf Cable Clock I/O

board, A-2

Cold reboot, 4-12

Committed burst (Bc), 5-23, 5-24, 5-25, 5-27, 5-32,

5-38, 5-39, 5-40, 5-41, 5-42, 5-49, 5-51, 5-52,

5-53

Committed information rate (CIR), 4-12, 4-13, 5-23,

5-24, 5-27, 5-32, 5-38, 5-39, 5-40, 5-42, 5-49,

5-51, 5-52, 5-53, 5-54

Computer Port Module-422B (CPM-422B), 5-103,

5-104, 5-106

Computer Port Module-High Speed (CPM-HS), 5-4,

5-7, 5-10, 5-19, 5-103, 5-104, 5-105, 5-106,

5-108, A-11, A-12

Computer Port Module Multiple Link (CPMML),

5-103, 5-104, 5-106

Computer Port Module Multiple Link-High Speed

(CPMML-HS), 5-103, 5-104

con (X.28 command), 9-18

Concentrator(s). See Also Multipurpose Concentrator

(MPC); Synchronous/Asynchronous

Multiplexer (SAM)

function within network, 1-3

maximum number of, 3-5

Congestion, 5-37, 5-38, 5-40

Congestion management, 5-24, 5-52

Connectionless network service (CLNS), 1-5, 1-10,

1-15, 2-8, 2-11, 4-3, 4-4, 4-15, 5-3, 5-64, 7-4

Connection-oriented network service (CONS), 1-15,

2-5, 2-11, 4-3, 4-4, 4-5, 4-12, 4-15, 5-12,

5-64, 6-3, 6-9, 7-16, 7-18, 8-3, 9-12

Connection(s),

DS3, 1-9, 4-4, 4-6, 4-17, 4-20, 5-3, 5-10, 5-28, 5-43,

5-56, A-9, A-10

E3, 1-9, 4-4, 4-6, 4-11, 4-15, 4-17, 4-20, 5-3, 5-10,

5-28, 5-43, 5-56

fiber, 1-9, 4-6, 4-17, 4-20, 5-10

for concentrators, 3-3

G.703/G.704/G.706, 4-6, 4-17, 4-20, A-10

RS-232-C, 1-9, 1-10, 2-51, 3-3, 3-10, 4-6, 4-18, 4-20,

5-8, 5-10, 5-11, 5-58, 5-84, 5-85, 5-88, 5-91,

5-92, 5-93, 5-96, A-7, A-10, A-12

RS-422/499, 4-6, 4-18, 4-20, A-12

10BASE-T, 5-10, 5-50

V.35, 1-9, 1-10, 4-6, 4-18, 4-20, 5-8, 5-10, 5-11, 5-21,

5-22, 5-29, 5-58, 5-84, 5-85, 5-88, 5-91, 5-93,

5-94, 5-95, 5-96, A-7, A-10, A-12

CONS. See Connection-oriented network service

(CONS)

Console display terminal, 2-33, 2-34

Console security, 9-6

Control Computer, 1-7, 2-6, 2-16, 2-29, 2-36, 5-13,

7-15, 7-17, 7-18, 8-17

console device, 2-51

Control Computer Module (CCM) configuration,

2-12, 2-36

dual configuration, 2-13, 2-14, 2-15, 2-16

ECPU configuration, 2-13

printer, 2-51


Index________________single configuration, 2-13, 2-14, 2-15, 2-16

spare parts, A-3

Control Computer Module (CCM), A-3

configuration, 2-12, 2-14, 2-16

Control unit (CU), 5-58, 5-59, 5-66, 5-67

Country Code (CC), 7-6, 7-12, 7-13

CPM-422B. See Computer Port Module-422B (CPM-

422B)

CPM-HS. See Computer Port Module-High Speed

(CPM-HS)

CPMML. See Computer Port Module Multiple Link

(CPMML)

CPMML-HS. See Computer Port Module Multiple

Link-High Speed (CPMML-HS)

CPY1, 5-4, 5-5, 5-9, 5-10, 5-19, 5-103, 5-104, 5-106,

5-107, A-7. See Also

Synchronous/Asynchronous Multiplexer 16-

port (SAM16)

Crankback, 8-13, 8-14, 8-18

Critical module(s), 1-7, 2-3

power, 1-6, 1-9

power consumption, 2-35, 2-36

redundancy, 2-12–2-17

CTG13 Extended Switch Module, 2-36, A-2

CTRM. See Clock/Trunk/Repeater Module (CTRM)

CU. See Control unit (CU)

Customer premises (CP) site preparation, 2-39, 2-46,

3-17

DData, clocking 5-75, 5-77

Data Country Code (DCC), 7-5

Data Exchange Interface/Subscriber Network Interface

(DXI/SNI), 1-10

Data link connection identifier (DLCI), 5-21, 5-22,

5-23, 5-24, 5-34, 5-37, 5-38, 5-50, 5-51, 5-52,

7-16

Data Network Identification Code (DNIC), 5-21, 5-34,

7-5, 7-7, 7-10, 7-11, 7-12, 7-13, 7-14, 9-21

Data service units (DSUs), 3-21, 4-13, 4-18, 5-58, 5-75,

5-77

Database,

addresses and, 10-4

audit, 10-4, 10-5, 10-6

basic structure defined, 10-3

components and, 10-4

concentrators or multiplexers and, 10-3

default routing and, 8-7, 10-7

groups and, 10-4, 10-7

hub node addresses, 8-7

interface modules and, 10-4

limits, 10-4–10-7

physical node and, 10-3

predefined destination (PDD) and, 10-7

resizing, 10-7

routing parameters and, 10-4

security parameters and, 10-4

space-saving measures, 10-7

trunk modules and, 10-4

Datakit II VCS (BNS-2000 VCS) interworking, 1-4,

1-5, 1-15, 4-4, 4-13, 8-17, 8-18

Datakit VCS interworking, 1-4, 1-15, 4-16, 5-56, 8-18

DCC. See Data Country Code (DCC)

DDCMP. See Digital Data Communications Message

Protocol (DDCMP)

DE. See Discard eligibility (DE) bits

Default routing. See Routing

DEFINITY 75/85 Communications System, 1-15

Delay, 5-65, 5-74, 5-75, 5-76, 5-77, 5-78

DESTINATION: prompt access, 9-3, 9-6, 9-24

diagnose frm-m2 (operations command), 5ZZ "5-48"

"5-48"

Diagnostic(s), nping test, 5-48

Digital Data Communications Message Protocol

(DDCMP), 1-10, 5-9, 5-61

Directory assistance, 1-12, 7-4, 7-9, 7-11

Discard eligibility (DE) bits, 5-40, 5-41, 5-54

Disk drive, 2-14, 2-15, 2-25, 2-26, 2-29, 2-35, 2-36

ECPU configuration, A-3

Distance limits for trunk modules, 4-17, 4-18

Distributed Queue Dual Bus (DQDB) protocol, 5-7,

5-15

DKAP module, 1-13, 3-4, 3-5, 5-4, 5-6, 5-10, 5-20,

5-103, 5-104, 5-106, 5-107, 5-108, 9-6,

9-24–9-25, A-11

DLCI. See Data link connection identifier (DLCI)

DNIC. See Data Network Identification Code (DNIC)

DQDB. See Distributed Queue Dual Bus (DQDB)

protocol


Index________________DS3 connections, 1-9, 4-4, 4-6, 4-17, 4-20, 5-3, 5-10,

5-28, 5-43, 5-56, A-9, A-10

DXI/SNI. See Data Exchange Interface/Subscriber

Network Interface (DXI/SNI)

EE1 interface limit, 2-32

E2A Module, 5-4, 5-8, 5-10, 5-104, 5-105, 5-108,

A-11, A-12

E3 connections, 1-9, 4-4, 4-6, 4-11, 4-15, 4-17, 4-20,

5-3, 5-10, 5-28, 5-43, 5-56

Earthquake bracing, 2-51, 3-20

Echoplexing, 2-32, 5-75, 5-84

ECPU configuration, 2-13, 2-15, 2-16, A-3

Editing characters, 7-19

EIA flow control, 5-5, 5-19, 5-58, 5-60, 5-61

Electrical characteristics of modules, 2-35, 5-108, 5-109

Electrical considerations,

48 VDC filtered battery, 2-50

fuses and central office (CO) frame, 2-51

input power feeder, 2-50

power distribution for central office, 2-50

power distribution for customer premises, 2-46

Series M1 Port Shelf modules and, 5-109

service requirements, 1-6, 1-9, 2-34, 3-14

Synchronous/Asynchronous Multiplexer 504-port

(SAM504), 3-20

Electromagnetic interference (EMI),

compliance with FCC regulations, 2-39, 3-17

Endpoint,

address, 1-12, 7-4, 7-5

address mapping, 7-14

as a permanently active port, 5-61

asynchronous, 5-61, 5-85, 5-89, 5-97, 5-102, 9-18

being a local device, 7-5

call origin/termination, 2-32

communication between, 1-4, 1-15, 4-15, 6-3

connection, 6-4

customer, 6-3, 6-4, 6-5

destination/termination, 7-7, 7-12, 8-17

flow control and, 5-61

frame relay, 5-22

grouping, 6-5, 6-6, 9-7, 9-8, 9-9

in an exchange, 7-7

load sharing and, 4-13

originating, 7-4, 8-17

outside of North America, 7-11, 7-12

permanent virtual circuit (PVC), 5-50

routing and, 8-3, 8-4, 8-7, 8-11, 8-12

security and, 9-3, 9-8, 9-11, 9-14, 9-16, 9-17, 9-18,

9-19, 9-21, 9-26

slot number, 2-32, 5-13

terminating, 5-13

traffic load between, 5-28

within North America, 7-10

Endpoint number (EPN), 7-5, 7-8, 7-10, 7-11, 7-13,

7-18, 9-31, 9-32

Endpoint(s),

frame relay, 5-37

traffic load between, 5-44

Enhanced Extension Shelf Cable Clock I/O board

(CNA8), A-2

enter node (operations command), 7-18

Environmental requirements for equipment, 2-36, 3-16

EPN. See Endpoint number (EPN)

Equipment room requirements, 2-36, 2-39, 3-16

Equipment specifications, 2-33, 3-13

Error,

detection/handling/recovery, 5-68

recovery of, 5-44

retransmissions and, 5-70

Escape code(s), 7-5, 7-6, 7-12

Ethernet connection, 1-10, 5-6, 5-29, 5-30, 5-31, 5-32,

5-50

Examples,

call screening security patterns, 9-11

connection-oriented network services, 6-6

crankback, 8-14

originating group security pattern, 9-10

Excess burst (Be), 5-23, 5-24, 5-25, 5-27, 5-32, 5-38,

5-39, 5-40, 5-41, 5-42, 5-49, 5-51, 5-52, 5-53

Exchange level, 7-5, 7-10

Extended Cable/Clock and RIB Status I/O Board

(CNA7), 2-24, 2-28, 2-35, A-2

Extended routing. See Routing

Extended Switch Module (CTG13), 2-24, 2-28, 2-35,

2-36, A-2


Index________________FFanout, 5-67, 5-72, 5-75

Feature packages, 1-11

FECN. See Forward explicit congestion notification

(FECN)

FEP. See Front-end processor (FEP)

Fiber connections, 1-9, 4-6, 4-17, 4-20, 5-10

Fiber trunks, 1-9, 1-10, 3-3

File transfer delay, 5-74

File transfer protocol (FTP), 5-30, 5-46

5ESS Switch, 1-12, 7-4, 9-30

Floor plan,

central office (CO), 2-49

single frame, 2-49

two frames, 2-50, 3-22

customer premises (CP), 2-47


(SAM504), 3-20

Flow control, 5-5, 5-13, 5-23, 5-28, 5-37, 5-44, 5-60,

5-61, 5-71

CPY1 and, 5-19, 5-20

grade of service (GOS) and, 5-12

TERM32 module and, 5-60

Format,

call address, 7-10

service address request, 7-11

Forward explicit congestion notification (FECN), 5-23,

5-36, 5-37

Frame Relay Module (FRM), 4-12, 5-4, 5-6, 5-10, 5-50,

5-103, 5-108, 7-18, A-11, A-12

planning, 5-21–5-33

traffic, 5-56

Frame size, 5-66, 5-72


throughput and, 5-64, 5-73

FRM. See Frame Relay Module (FRM)

FRM-M2. See M2 Frame Relay Module (FRM-M2)

Front-end processor (FEP), 5-71

frport, 5-54, 9-26

FTP. See File transfer protocol (FTP)

Full duplex transmission, 5-6, 5-19, 5-20, 5-58, 5-91,

5-92, 5-93

Full (non-default) routing. See Routing

GG.703/G.704/G.706 connections, 4-6, 4-17, 4-19, 4-20,

A-10

GAR. See Group Address Resolver (GAR) module

GOS. See Grade of service (GOS)

Grade of service (GOS), 5-12, 5-19, 5-60, 5-64, 5-68,

5-70, 5-71, 5-72, 5-73, 5-74, 5-81, 5-82, 5-84,

5-85

Grounding requirements, 2-51

Group Address Resolver (GAR) module, 5-4, 5-7, 5-11,

5-49, 5-105, 5-108, A-11, A-12

Group(s),

addressing and, 6-3, 6-10, 8-5, 8-6

database and, 1-13, 10-4, 10-7

grouping endpoints, 6-10

?lcl, 7-9, 7-18

limit per node, 9-7

local, 6-4, 6-5, 6-9, 7-16

name, 7-16, 7-19

network access, 7-19, 9-6

?nmsiep, 7-18

originating, 6-10, 7-16, 7-17, 7-19, 9-3, 9-7, 9-8

originating group security, 1-13, 6-10, 9-7

password sharing, 9-7

receiving, 6-10, 7-16, 7-17, 7-19, 8-5, 9-7, 9-8

reports and, 7-17

restrictions, 7-19

routing and, 1-12, 6-3, 6-4, 6-5, 6-8

select, 7-19, 9-6

?skimiep, 7-18

?smdsbac, 7-18

?smdsbil, 7-18

special, 7-16

trunk, 6-4, 6-6, 6-8, 7-16, 7-17, 7-18, 8-3, 8-5, 8-6,

8-9, 9-8

two-way, 6-10, 7-12, 7-16, 7-17, 7-18, 8-5, 9-8

HHalf duplex transmission, 5-20, 5-58, 5-60, 5-61

Hardware, and flow control, 5-13

HDLC. See High Level Data Link Control (HDLC)

protocol

Hierarchical default routing. See Routing


Index________________High availability. See Redundancy

High Level Data Link Control (HDLC) protocol, 5-9,

5-62, 5-65, 5-75, 5-77

Hop count, 8-16, 8-18

Host(s),

access permissions, 7-17

acknowledgement timer, 5-71

as receiving devices, 7-10

broadcast and, 5-66

buffer flushing and, 5-71

calls screening security and, 9-11, 9-12, 9-13

computer, 2-6, 6-3

directory assistance and, 7-12

fanout and, 5-67

LAN Protocol Module (LPM) and, 5-55, 5-56

multiplexed interfaces for, 2-32, 5-7, 5-13, 5-19, 9-17,

9-24


Network Access Control System and, 9-22

passwords and, 9-5

placement of in node slot, 2-32

processing, 5-60, 5-61, 5-78

protocols, 5-61

receiving group and, 7-17

remote hosts and frame relay, 5-31, 5-32, 5-48

Synchronous 8-port (SYNC8) module (bsc3270) and,

5-58

timeout values, 5-74

Transparent Synchronous Module 8-port (TSM8) and,

5-61

two-way groups and, 7-18

X.25, 7-4, 9-14, 9-18, 9-19, 9-30, 9-32

Hunt group, 9-17, 9-18

IICC. See Intershelf Cable/Clock (ICC)

ICI. See Inter-Carrier Interface (ICI)

ICN. See International interlock code number (ICN)

Information Systems Network (ISN), 1-4, 1-15, 4-7,

4-16

Input/output (I/O) cable egress, node shelf 2-39

Integrated Services Digital Network (ISDN), 7-4, 7-6

Inter-Carrier Interface (ICI), 7-18

Interface module(s),

addressing of, 7-15

as a connection point, 6-4

asynchronous, 1-10, 5-4, 5-5, 5-19, 5-20, 5-57, 5-60,

5-61, 5-82–5-83, 5-103, 5-108, 5-109

concentrators and, 3-3

customer programmable, 1-10, 5-4, 5-6, 5-20, 5-108,

9-24–9-25

database and, 10-3, 10-4

endpoints and, 9-17

flow control and, 5-13


grade of service (GOS) and, 5-12, 5-13, 5-82

groups and, 7-17

LAN interconnect, 1-10, 5-4, 5-6, 5-21–5-33,

5-50–5-56, 5-103, 5-108

measurements data, 5-14

multiplexed host, 1-10, 5-4, 5-19, 5-104, 5-108, 9-19

node slot, 7-15

ports versus modules, 5-14

power, 1-6, 1-9

service planning, 1-10

software download, 5-13

spare parts information, A-11–A-12

special purpose, 1-10, 5-4, 5-8, 5-10, 5-104, 5-105,

5-108, 5-109, A-11

standards, 1-10, 5-4, 5-84–5-102, 5-104, 5-106,

5-109, 6-6, 9-19

switched bisynchronous, 1-10, 5-4

Switched Multimegabit Data Service (SMDS), 1-10,

5-4, 5-7, 5-15, 5-49, 5-105, 5-108

synchronous, 1-10, 5-4, 5-9, 5-19, 5-20, 5-58–5-59,

5-60, 5-61, 5-62–5-81, 5-107, 5-109

Transparent Synchronous Module 8-port (TSM8),

5-61

Interface Repeater Unit (IRU), A-5, A-6

International interlock code number (ICN), 9-21

International prefix, 7-5

Internet Protocol (IP), 5-30, 5-32, 5-46, 5-48

addressing, 5-55

alternate routing, 5-55

routing, 5-54, 9-26

Intershelf Cable/Clock (ICC), 2-28


Index________________Interworking, 5-43

BNS-1000, 1-4, 1-15, 4-7, 4-13, 8-17

BNS-2000, 1-4, 1-5, 1-15, 4-4, 4-7, 4-13, 4-15, 8-17,

8-18

BNS-2000 VCS (Datakit II VCS), 1-4, 1-5, 4-4, 4-13,

8-17, 8-18,

crankback and, 8-18

Datakit VCS, 1-4, 1-15, 4-16, 8-18

DKAP and, 5-20

hop count and, 8-18

Information Systems Network (ISN), 1-4, 1-15, 4-16

LAN Communications Systems (LCS), 5-81

public data network (PDN), 9-14

route advance and, 8-18

Synchronous/Asynchronous Multiplexer (SAM), 5-81

Transparent Synchronous Module 8-port (TSM8),

5-70, 5-81

Transparent Synchronous Module-T1 (TSM-T1), 5-81

trunk channel administration and, 4-16

X.25 and, 9-14

Intranodal throughput (point-to-point), 5-73

IP. See Internet Protocol (IP)

IRU. See Interface Repeater Unit (IRU)

ISDN. See Integrated Services Digital Network (ISDN)

ISN. See Information Systems Network (ISN)

LLAN Communications Systems (LCS), 1-10, 5-57, 5-81

LAN Protocol Module (LPM), 5-4, 5-6, 5-11,

5-50–5-56, 5-103, 5-108, A-11, A-12

security, 5-54, 9-26

lanport, 5-54, 9-26

?lcl group, 7-18

LCS. See LAN Communications Systems (LCS)

LIM. See Link Interface Module (LIM)

Line speed (LS), 5-38, 5-39, 5-43, 5-44, 5-49, 5-75,

5-77

Link access procedure for frame mode (LAPF), 5-44,

5-45, 5-46, 5-47, 5-48

Link Interface Module (LIM), 4-3, 4-4

addressing, 7-15

Load sharing, 4-13

Local area network (LAN), 2-32, 5-44, 5-49, 7-17, 9-26

interconnect, 5-50

Local level, 7-5, 7-10

Local management interface (LMI), 5-37

LPM. See LAN Protocol Module (LPM)

MM2 Frame Relay Module (FRM-M2), 1-5, 2-11, 5-4,

5-6, 5-10, 5-34, 5-108, A-11, A-12

Maintenance and Redundancy Control (MRC) function,

2-12, 2-13, 2-14, 2-15, 2-16, 2-19, A-3, A-4

Maintenance and Redundancy Control Module

(MRCM), 1-7, 2-5, 2-14, 2-19, 2-24, 2-26,

2-27, 2-29, 2-30, 2-35, 2-36, A-4, A-5

MAR. See Maximum arrival rate (MAR)

Maximum arrival rate (MAR), 5-49

Maximum transmission unit (MTU), 5-30, 5-46, 5-52

Mean time between failures (MTBF), 2-15

Media access control (MAC), 5-48

Mesh network, 8-8

Migration, 1-14

hardware considerations, 4-11

Modem(s), 1-5, 1-10, 3-5, 4-17, 5-58

as a customer end device, 6-3

call-back/dial-back, 3-7, 9-24

dial-in, 3-21, 7-17, 9-7, 9-22, 9-24

dial-out, 3-21, 9-24

groups and, 6-4, 6-10, 7-17

processing delay and, 5-75, 5-77

Modular cabinet(s), 1-6, 2-41

Base Power Unit and, 2-23, 2-33

control cabinet, 2-6

data switching rate, 2-4

module placement, 2-31, 2-32

site preparation, 3-21

slot number, 2-25, 2-29, 3-9 5-37

Module(s). See Critical module(s); Interface

module(s); Trunk module(s)

MPC. See Multipurpose Concentrator (MPC)

MRC function. See Maintenance and Redundancy

Control (MRC) function

MRCM. See Maintenance and Redundancy Control

Module (MRCM)

MSM. See Multispeed Module (MSM)

MTBF. See Mean time between failures (MTBF)


Index________________MTU. See Maximum transmission unit (MTU)

Multibridged application, 5-72

Multiplexed hosts. See Computer Port Module-High

Speed (CPM-HS)

Multiplexer(s). See Also Synchronous/Asynchronous

Multiplexer (SAM)


Multipoint bridging, 5-66, 5-67

Multipurpose Concentrator (MPC), 1-8, 3-3, 3-13, 3-14,

3-15, 3-16, 3-17, 3-18, A-1, A-6

address format, 7-15

CO equipment structure, 3-9

database and, 10-3

environmental operating limits, 3-16

link interface modules, 4-3, 4-7, 10-4

multiplexed host interfaces and, 5-19

power, 1-9, 3-14, 3-15

redundancy, 1-9

spare parts, A-6

Multispeed Module (MSM), 5-4, 5-5, 5-11, 5-57, 5-57,

5-103, 5-104, 5-106, 5-108, A-11, A-12

NNational destination code (NDC), 7-6

National Number (NN), 7-5

National (Significant) Number (N(S)N), 7-5, 7-6, 7-12,

7-13

NDC. See National destination code (NDC)

Network,

access, 7-19, 9-6–9-7

building blocks, 1-3

design, 8-13

efficiency, 5-79

feature packages, 1-11

fully connected, 8-17

load, 5-28–5-29

logical channels, 5-12

mesh, 8-8

performance, 5-72

private line connection delay, 5-74

ring, 8-8, 8-17

security planning, 9-3–9-34

traffic, 4-11, 4-12, 5-12, 5-62

transport delay, 5-74, 5-75

Network Access Control System, 9-7, 9-22–9-24

Network efficiency, 5-46–5-47

Network load, 5-44–5-45

Network ping, 5-48

Network Terminal Number (NTN), 7-5, 7-13

?nmsiep group, 7-18

NN. See National Number (NN)

Node(s). See Also Modular cabinet(s); Series M1

Shelf; Series M2 Shelf

alias, 7-9

availability, 1-7

backplane, 1-4, 2-6, 2-7, 2-8, 2-25, 2-31, 2-32, 5-53,

5-75, 5-78

bandwidth, 1-4, 2-3, 2-5, 2-32, 4-14

compatibility/interworking, 1-4

critical/redundant modules, 2-3, 2-12–2-17, 2-25,

2-26, 2-35, 2-36

endpoint, 7-12

equipment, 1-6

feature packages, 1-11

function with network, 1-3

hub, 8-4, 8-7

identifying, 7-18

interworking, 5-34, 5-43

leaf, 8-4

minimum configuration, 2-44

National Country Code (NCC), 7-6

overall capacity, 2-30

performance degradation, 1-5

power, 1-6

prefix, 7-5, 7-12, 7-13

redundancy, 1-7

round-trip delay, 1-5

services, 1-5

slot numbers, 7-14

types, 1-4

Non-default (full) routing. See Routing

N(S)N. See National (Significant) Number (N(S)N)

NTN. See Network Terminal Number (NTN)

Numbering plan(s),

X.121 E.164 Numbering Plan, 7-4, 7-5, 7-12, 7-13,

7-14

X.121 International, 7-4, 7-5, 7-12, 7-13

X.121 North American Numbering Plan (NANP),

7-4, 7-5, 7-6, 7-12


Index________________OOriginating group security, 1-13, 9-7, 9-9

PPacket assembler/disassembler (PAD), 5-8, 5-19, 5-84,

5-97

Packet segmentation, 5-87

Packet size, 5-87, 5-88, 5-89, 5-91, 5-97, 5-100, 5-101,

5-102

Packet-switched public data networks (PSPDNs), 1-10,

1-12, 4-3, 5-4, 7-4, 7-6, 10-4

PAD. See Packet assembler/disassembler (PAD)

Password(s), 9-5, 9-7

for network access, 7-19

Network Access Control System and, 9-23

PC. See Personal computer (PC)

PDB. See Power board distribution (PDB)

PDD. See Predefined destination (PDD)

PDE. See Portable development environment (PDE)

software

PDN. See Public data network (PDN)

PDSC. See Power distribution service cabinet (PDSC)

Performance, 5-44

Frame Relay Module (FRM) issues, 5-21

large frame sizes, 5-28, 5-43

network, 5-72

requirements for, 5-56

throughput and, 5-72

Peripheral equipment, 2-51

Permanent virtual circuit (PVC), 4-12, 5-21, 5-22, 5-23,

5-34, 5-37, 5-38, 5-50, 5-51, 5-87, 5-100

Personal computer (PC),

database limits and, 7-9


Personal user authentication device, 9-23

Physical Layer Convergence Protocol (PLCP), 5-7,

5-15

Pipelining, 4-13

PLCP. See Physical Layer Convergence Protocol

(PLCP)

PNIC. See Private Network Identification Code (PNIC)

Point-to-Point Protocol (PPP), 5-57

Port shelves, 2-6

Portable development environment (PDE) software,

5-20

Port(s),

addressing, 5-51, 5-56

control unit (CU) combinations and, 5-58

for physical Ethernet LAN, 5-50

group, 7-16

measurements, 5-12, 5-14

screening filters, 5-54

usage guidelines, 5-12, 5-14

virtual frame relay, 5-50

Power,

configurations, 2-16

consumption, 1-6, 1-9, 2-16

node, 1-6

Power board distribution (PBD), 2-50

Power distribution service cabinet (PDSC), 2-50

Power supply, 1-6, 1-7

concentrators and, 1-9, 3-5

Multipurpose Concentrator (MPC), 3-7, 3-9

Series M1 Shelf, 2-16

Series M2 Shelf, 2-16

Synchronous/Asynchronous Multiplexer (SAM), 3-7


(SAM16), 3-7


(SAM64), 3-7


(SAM504), 3-7, 3-11, 3-20

uninterruptible, 2-39, 2-41

Voice Data Multiplexer-Synchronous/Asynchronous

Multiplexer 504-port (VDM-SAM504), 3-7

PPP. See Point-to-Point Protocol (PPP)

Predefined destination (PDD), 3-7, 4-12, 5-5, 5-50,

5-51, 5-61, 5-81, 7-14, 9-7, 9-8, 10-7

Prefix(es),

international, 7-5

local node, 7-5, 7-13

used in addresses, 7-5

Printer(s), 1-10, 2-51, 5-58, 6-3, 7-17

Private Data Network Identification Code (PNIC), 7-13

Prompt, DESTINATION 7-11

Propagation delay, 5-77


Index________________Protocol(s),

Binary Synchronous Communications (BSC), 1-10,

5-9

Burroughs/NCR Poll/Select, 1-10, 5-9

conversion, 1-10

customized protocol support, 5-6

data transfer, 5-82

Digital Data Communications Message Protocol

(DDCMP), 1-10, 5-9, 5-61

Distributed Queue Dual Bus (DQDB), 5-7, 5-15

High Level Data Link Control (HDLC), 1-10, 5-9,

5-62, 5-65, 5-75, 5-77

host, 5-61

internal, 5-12, 5-20, 5-24, 5-52, 5-60

multiprotocol encapsulation (frame relay), 5-30, 5-46

overhead of, 5-62

Physical Layer Convergence Protocol (PLCP), 5-7,

5-15

Point-to-Point Protocol (PPP), 5-57

Serial Line Interface Protocol (SLIP), 5-57

Synchronous Data Link Control (SDLC), 1-10, 5-9,

5-62, 5-65, 5-72, 5-75, 5-77

Transmission Control Protocol/Internet Protocol

(TCP/IP), 5-65

UNISCOPE, 1-10, 5-9

X.75, 9-21

PSPDN. See Packet-switched public data network

(PSPDN)

Public Data Network Identifier (PDNID), 7-5

Public data network (PDN), 1-12, 4-3, 5-4, 7-4, 7-14,

9-14, 9-19, 9-21, 9-31, 9-32, 10-4

PVC. See Permanent virtual circuit (PVC)

RRecovery. See Also Redundancy

Control Computer, 2-14, 2-15


link, 3-7

of errors, 5-20, 5-28, 5-58, 5-60, 5-68, 5-71

Session Maintenance and, 4-14

Redundancy,

central office (CO) frame power feeds, 2-51

concentrator, 1-9

Control Computer, 1-7, 2-15, 2-17, 2-19, 2-26

link, 3-5, 3-6

node options, 1-7, 2-3

power supply, 2-16, 2-25, 2-29, 3-7

routing paths, 1-7, 8-11, 8-12, 8-13

Series M1 Shelf, 2-24, 2-30

Switch, 1-7, 2-4, 2-17, 2-28, 3-9

trunks, 1-7, 8-11, 8-12

Reference input boards (RIB)/Status I/O board (CNA7),

2-36

Remote maintenance, 2-16

Repeater module, 2-6, 2-19, 2-25, 2-26, 2-36, 3-5, A-3,

A-5, A-6

Reports, 7-17

Request to send (RTS), 5-13

Ring network, 8-8, 8-9, 8-17

Round-robin service, 7-17, 7-18, 7-19

Route advance, 8-15, 8-18

Routing,

addresses and, 7-4, 7-7, 7-9, 7-12, 7-13, 7-14, 8-3

alternate, 1-7, 8-3, 8-11, 8-12, 8-13, 8-16

alternate Internet Protocol (IP), 5-55

automatic rerouting, 1-7

call setup, 8-17

cold rebooting and addressing, 4-12

crankback, 8-18

default, 5-55, 6-8, 7-9, 8-4, 8-4–8-7, 9-8, 10-7

definition, 1-12, 8-3

extended, 8-13, 8-17, 8-18

full (non-default), 1-12, 6-6, 6-8, 8-3, 8-8

groups and, 6-4, 6-5, 8-3, 8-9, 8-10

hierarchical default, 1-12, 6-6, 8-3

hop count, 8-18

Internet Protocol (IP), 5-54

interworking and, 4-15

primary, 8-13

protocols for, 5-31

strategies, 6-4, 6-6

Switched Multimegabit Data Service (SMDS) trunk

upgrades and, 4-11

tables for, 8-17

variations, 1-12, 8-3

Routing protocols, 5-47

RS-232-C connections, 1-9, 1-10, 2-51, 3-3, 3-10, 4-6,

4-18, 4-20, 5-8, 5-10, 5-11, 5-58, 5-84, 5-85,

5-88, 5-91, 5-92, 5-93, 5-96, A-7, A-10, A-12


Index________________RS-449/422 connections, 4-6, 4-18, 4-20, A-12

RTS. See Request to send (RTS)

SSA. See Service Area (SA)

SAM. See Synchronous/Asynchronous Multiplexer

(SAM)

SCSI. See Small Computer Systems Interface module

(SCSI/DKI)

SDLC. See Synchronous Data Link Control (SDLC)

protocol

SDLC8. See Synchronous Data Link Control 8-port

(SDLC8) module

Security, 7-17

call screening, 9-11–9-13

closed user group (CUG), 9-6, 9-14, 9-15, 9-16, 9-30

security checking rules, 9-18

console, 9-6

default routing and, 9-27


DKAP module software, 9-24–9-25

LAN interconnection and, 9-26

LAN Protocol Module (LPM), 5-54

Network Access Control System, 9-22–9-24

network features, 9-6–9-27

operational, 9-5

originating group, 9-7, 9-9, 9-27

patterns, 9-9, 9-10

personnel, 9-5

physical, 9-4

planning examples, 9-27–9-34

planning overview, 1-13, 9-3, 9-5, 9-34

requirements, 9-4

trunk call screening, 9-13, 9-33

X.25 calls barred, 9-19–9-20

X.75, 9-20–9-22

Select group, 9-11

Serial Line Interface Protocol (SLIP), 5-57

Series M1 Shelf, 1-6, 2-11, 2-20, 2-44, 2-49, 2-51, A-1

capacity, 2-29

electromagnetic compliances, 2-37

input power compliance, 2-38

maximum configuration, 2-21

module addresses, 2-25

physical specifications, 2-33

power supply, 2-16

safety compliances, 2-38

slot number, 2-25

spare parts, A-3–A-5, A-9–A-12

Series M2 Shelf, 1-6, 2-11, 2-20, 2-44, 2-49, 2-51, 5-7,

A-1

capacity, 2-25

electromagnetic compliances, 2-37

input power compliance, 2-38

maximum configuration, 2-22

physical specifications, 2-33

power supply, 2-16

safety compliances, 2-38

spare parts, A-2

Service Area (SA), 7-5, 7-8, 7-10, 7-11

Service Region (SR), 7-5, 7-8, 7-10, 7-11

Session Maintenance, 4-14

SFT. See Standard Fiber Trunk (SFT)

Shelf, 2-11

Base Power Unit and, 2-19

capacity, 2-25, 2-29

central office (CO) frame and, 2-19

configurations, 2-17

Control Computer and, 2-14, 2-15, 2-25

module placement, 2-31

number of/numbering, 2-19

numbering recommendations, 2-23

power, 2-35

rules for location, 2-17

rules for number configured, 2-17

site preparation, 2-42–2-43

slot number, 2-25

spare parts, A-3–A-5, A-9–A-12

upgrade, 2-11

Simplex I/O, Control Computer Module (CCM)

configuration, 2-12, 2-14, A-3

Site preparation,

all sites, 2-39, 2-41, 3-17

central office (CO), 2-49, 2-51

customer premises (CP), 2-46

Multipurpose Concentrator (MPC), 3-18

planning, 2-39, 3-17


(SAM16), 3-24



Index________________(SAM64), 3-23


(SAM504), 3-20

?skimiep group, 7-18

SLIP. See Serial Line Interface Protocol (SLIP)

SLM. See Synchronous Link Module (SLM)

Slot numbers, 7-14

Small Computer Systems Interface module

(SCSI/DKI), 2-13, 2-15, 2-25, 2-29, 2-35,

2-36, A-3

SMDS. See Switched Multimegabit Data Service

(SMDS)

?smdsbac group, 7-18

?smdsbil group, 7-18

Spare parts, A-1–A-12

Special characters, 7-19

Speed mismatch, 5-71

Speedcall(s), 1-12, 7-4, 7-9

sphaddr (operations command object), 7-6

Splice, 8-17

SR. See Service Region (SR)

SSM4. See Stratum 4 Clock (SSM4)

Standard Fiber Trunk (SFT), 4-4, 4-5, 4-6, 4-15, 4-19,

4-20, 5-6, 5-64, 5-77, A-10

Standard Wire Trunk (SWT), 1-15, 4-4, 4-5, 4-6, 4-12,

4-12–4-13, 4-15, 4-19, 4-20, 5-6, 5-28, 5-43,

5-64, 5-77, A-9, A-10

Standards, American National Standards Institute

(ANSI),

T1.606, 5-40

Star architecture. See Architecture

StarKeeper II Network Management System (NMS),

1-11, 1-14

Network Access Control (NAC), 9-23

special group, 7-18

StarKeeper II NMS. See StarKeeper II Network

Management System (NMS)

Stratum 4 Clock (SSM4), 2-28, 2-35, 2-36, A-2

Stratum 4 Clock (STR4), 2-28, 2-35, 2-36, A-2

STR4. See Stratum 4 Clock (STR4)

Subnet mask, 5-55

as an administration option, 5-50

Subscriber Number (SN), 7-6

Switch module (TN1002B), 3-15, A-6

Switch module (TN2099), 1-7, 2-6, 2-15, 2-17, 2-19,

2-24, 2-26, 2-36, A-3

Switched Multimegabit Data Service (SMDS), 1-5,

2-28, 2-32, 4-3, 5-3, 5-4, 5-49, 7-4, 9-3, 10-4

Access Interface (AI) modules and, 5-7, 5-15

ICI trunking, 4-15

interworking, 5-105

private interLATA trunking, 4-11

trunk upgrades, 4-11

Switched virtual circuit (SVC), 5-87, 5-100, 9-8

Switchover, automatic 2-17

SWT. See Standard Wire Trunk (SWT)

SYNC8. See Synchronous 8-port (SYNC8) module

(bsc3270)

Synchronous 8-port (SYNC8) module (bsc3270), 5-4,

5-9, 5-11, 5-58, 5-58–5-59, 5-109, A-11,

A-12

Synchronous Data Link Control (SDLC) protocol, 5-9,

5-62, 5-65, 5-72, 5-75, 5-77

Synchronous Link Module (SLM), 1-15, 5-4, 5-8,

5-104, 5-105, 5-109, A-11, A-12

Synchronous/Asynchronous Multiplexer (SAM), 1-7,

3-3, 4-9

address format, 7-15, 7-16

buffer flushing and, 5-70

database and, 10-3

environmental operating limits, 3-16

interworking, 5-81

link interface modules, 4-4, 4-7, 10-4

maximum number of, 3-5

power, 1-9, 3-14

redundancy, 1-9

spare parts, A-7, A-8


(SAM8), 5-103, 5-106, 5-107


(SAM16), 1-8, 3-13, 3-14, 3-16, 3-17, 3-24,

4-3, 4-13, 4-14, 5-4, 5-5, 5-9, 5-10, 5-19,

5-57, 5-103, 5-106, 5-107, A-1, A-7


(SAM64), 1-8, 3-13, 3-14, 3-16, 3-17, 3-23,

4-3, 4-13, 4-14, 5-9, 5-57, 5-60, A-1, A-7,

A-10


Index________________Synchronous/Asynchronous Multiplexer 504-port

(SAM504), 1-8, 3-13, 3-14, 3-16, 3-17, 3-19,

3-20, 3-21, 4-3, 4-14, 5-57, 5-60, A-1, A-8

Synchronous/Asynchronous Multiplexer Dual Link

(SAMDL) module, 4-6, 4-13, 4-20, A-7, A-9,

A-10

Synchronous/Asynchronous Multiplexer Multiple Link

(SAMML) module, 4-4, 4-5, 4-6, 4-13, 4-15,

4-18, 4-19, 4-20, A-9, A-10

Synchronous/Asynchronous Multiplexer Multiple Link

Node (SAMML-N) module, A-10

Synchronous/Asynchronous Multiplexer Single Link

(SAMSL) module, 4-4, 4-5, 4-6, 4-14, 4-15,

4-18, 4-19, 4-20, 7-16, A-9, A-10

Synchronous/Asynchronous Multiplexer Single Link

Node (SAMSL-N) module, 4-6

TT (time) measurement period, 5-39

T1 interface limit, 2-32

TACACS protocol, 9-23

Tape drive, 2-14, 2-29, 2-37, 2-41

external, 2-15, 2-16, 2-19, A-3

internal, 2-15, 2-16, 2-19, 2-25, 2-26, 2-35, 2-36, A-3

TCC. See Telephone Country Code (TCC)

TCP/IP. See Transmission Control Protocol/Internet

Protocol (TCP/IP)

Telephone Country Code (TCC), 7-6, 7-12, 7-13

10BASE-T connections, 5-10, 5-50

TERM32 module, 3-4, 3-5, 3-7, 3-10, 3-11, 3-20, 5-4,

5-5, 5-9, 5-11, 5-60, 5-103, 5-104, 5-106,

5-107, A-7, A-8, A-11

Terminal Module 6-port (TY-6), 5-4, 5-5, 5-11,

5-82–5-83, 5-103, 5-104, 5-106, 5-109

Terminal Module 12-port (TY-12), 5-4, 5-5, 5-11, 5-19,

5-57, 5-82–5-83, 5-103, 5-104, 5-106, 5-109,

A-11, A-12

Terminal(s), 1-10, 2-6, 2-32, 5-13, 5-57, 5-58, 5-59,

5-74, 9-7, 9-18

as a console display, 2-33, 2-34

group and, 7-17

Throughput, 5-21, 5-28, 5-35, 5-44, 5-64, 5-72, 5-73,

5-74, 5-97, 5-99, 5-100

tuning, 5-23, 5-24, 5-28, 5-51, 5-52, 5-56, 5-65

Time-to-repair (TTR), 2-15

TNM. See Total Network Management (TNM)

Total Network Management (TNM), 5-8

Traffic, 5-38, 5-40, 5-43, 5-44, 5-47, 5-48, 5-49

bursts, 2-32, 5-64

volume as networking consideration, 8-13

Transmission Control Protocol/Internet Protocol

(TCP/IP), 1-10, 5-6, 5-29, 5-30, 5-31, 5-44,

5-46, 5-48, 5-65, 9-22

Transparent Synchronous Module 8-port (TSM8), 5-4,

5-5, 5-9, 5-11, 5-61, 5-103, 5-104, 5-106,

5-107, 5-109, A-11, A-12

Transparent Synchronous Module-T1 (TSM-T1), 5-4,

5-9, 5-11, 5-62–5-81, 5-107, 5-109, A-11,

A-12

Trunk call screening, 9-12, 9-13, 9-33, 9-34

Trunk channel administration, 4-16

Trunk module(s), 5-37, 5-43, 5-44, 5-48, 5-49. See

Also Connectionless network service (CLNS);

Connection-oriented network service (CONS)

backbone, 5-31, 5-47, 5-56

bandwidth, 8-13

characteristics, 4-18

coaxial, 1-9, 4-3, 4-17

compatibilities, 8-18

connection standards, 4-17, 4-20

crankback, 8-18

delay, 5-76, 5-77

distance limits, 4-17

fiber, 1-9, 4-3, 4-15

frame relay traffic, 5-28, 5-43


HS-Trunk, 4-6, A-9, A-10

internodal, 4-3, 4-4, 5-52

Link Interface Module (LIM), 4-3, 4-4

overall planning, 1-9

power, 1-6, 1-9

route advance, 8-18

SAMDL, 4-13–4-14, A-7, A-9, A-10

SAMML, 4-4, 4-5, 4-6, 4-15, 4-19, A-9, A-10

SAMML-N, A-10

SAMSL, 4-4, 4-5, 4-6, 4-15, 4-19, 7-16, A-9, A-10

SAMSL-N, 4-6, 4-19, A-9

selection, 4-14

session maintenance traffic and, 4-14


Index________________SMDS traffic and, 4-14

speeds, 5-31, 5-47, 5-64, 8-13

Standard Fiber Trunk (SFT), 4-4, 4-5, 4-6, 4-15, 4-19,

4-20, 5-6, 5-64, 5-77, A-10

Standard Wire Trunk (SWT), 1-15, 4-4, 4-5, 4-6,

4-12, 4-12–4-13, 4-15, 4-19, 4-20, 5-6, 5-28,

5-43, 5-56, 5-64, 5-77, A-9, A-10

T1-Trunk, 4-6, A-9, A-10

trunk channel administration and, 4-16

Trunk-64, 4-4, 4-5, 4-6, 4-15, 4-20, A-9

Trunk-DDS, 4-16, 4-20

Trunk-E3, 1-5, 4-11, 5-3, 5-28, A-9, A-10

Trunk-E3A, 1-5, 4-4, 4-5, 4-6, 4-11, 4-15, 4-19, 4-20,

5-43, 5-56, A-9, A-10

Trunk-E3S, 4-5, 4-6, 4-11, 4-15, 4-19, 4-20, 5-43,

5-56, A-9, A-10

Trunk-HS, 4-4, 4-5, 4-6, 4-15, 4-16, 4-20, 5-77, 7-16,

A-9, A-10

Trunk-PQ, 4-4, 4-5, 4-6, 4-12, 4-12–4-13, 4-15, 4-19,

4-20, 5-6, 5-28, 5-43, 5-56, A-9, A-10

Trunk-T1, 1-15, 4-3, 4-4, 4-5, 4-6, 4-11, 4-15, 4-16,

4-19, 4-20, 5-28, 5-56, 5-64, 5-77, 7-16, A-9,

A-10

Trunk-T3, 1-5, 4-6, 4-11, 5-3, 5-28, A-9, A-10

Trunk-T3A, 1-5, 4-4, 4-5, 4-11, 4-15, 4-19, 4-20,

5-43, 5-56, A-9, A-10

Trunk-T3I, 2-32, 4-4, 4-5, 4-6, 4-11, 4-15, 4-19, 4-20,

A-9, A-10

Trunk-T3S, 4-5, 4-6, 4-11, 4-15, 4-19, 4-20, 5-43,

5-56, A-9, A-10

type and processing delay, 5-77

wire, 1-9, 4-3, 4-15

TSM8. See Transparent Synchronous Module 8-port

(TSM8)

TSM-T1. See Transparent Synchronous Module-T1

(TSM-T1)

TTR. See Time-to-repair (TTR)

TY6. See Terminal Module 6-port (TY-6)

TY12. See Terminal Module 12-port (TY-12)

UUID. See Unique identifier (UID)

Unauthorized access, 9-3

Unique identifier (UID), 9-23

UNISCOPE protocol, 1-10, 5-9

VV.35 connections, 1-9, 1-10, 4-6, 4-18, 4-20, 5-6, 5-8,

5-10, 5-11, 5-21, 5-22, 5-29, 5-58, 5-84, 5-85,

5-88, 5-91, 5-93, 5-94, 5-95, 5-96, A-7, A-10,

A-12

Virtual path (VP), 4-11

Voice Data Multiplexer-Synchronous/Asynchronous

Multiplexer 504-port (VDM-SAM504), 1-8,

3-13, 3-14, 3-16, 3-17, 3-21

VP. See Virtual path (VP)

Vulnerability analysis, 9-4

WWide area network (WAN), 5-49, 5-50

Window size, 5-24, 5-49, 5-52, 5-66, 5-71, 5-81, 5-87,

5-88, 5-89, 5-91, 5-97, 5-100, 5-101, 5-102

XX.121 E.164 Numbering Plan, 7-4, 7-5, 7-12, 7-13,

7-14

X.121 International Numbering Plan, 7-4, 7-5, 7-12,

7-13

X.121 North American Numbering Plan (NANP), 7-4,

7-5, 7-12

X.25 Module, 5-4, 5-8, 5-84, 5-104, 5-109, 7-14, A-11,

A-12

X.25 Standard,

CCITT Recommendations, 5-85

numbering plans, 7-4, 7-13, 7-14

X.3 PAD parameter, 5-20

X.3 profile, 5-84

X.25P Module, 5-4, 5-8, 5-85–5-96, 5-104, 5-109, 7-14,

A-11, A-12

X.75 Module, 5-4, 5-8, 5-97–5-102, 5-104, 5-109, 7-14,

A-11

X.75 protocol, 9-21

XON/XOFF flow control, 5-5, 5-13, 5-19, 5-23, 5-37,

5-60, 5-61


Documents

DATA NETWORKING PRODUCTS PLANNING GUIDE