I E N Pr o d u c t
D e s i g n Re f e r e n c e
Ver s i o n 1 . 6
2851 West Kathleen Road Phoenix, Arizona 85023 USA
Corporate Telephone: (602) 504-5000 Corporate Fax: (602) 866-5380
TRADEMARKS: Hypercom has attempted throughout the Integrated Enterprise Network Reference Library to distinguish proprietary trademarks from descriptive terms by following the capitalization style used by the manufacturer.
The Integrated Enterprise Network is a trademark. Hypercom and the Hypercom logo are registered trademarks of Hypercom Corporation. All other products or services mentioned in this document are trademarks, service marks, or registered
trademarks of their respective owners.
Every effort has been made to supply complete and accurate information. However, Hypercom assumes no responsibility for its use, nor any infringement of the intellectual property rights of third parties which would result from such use.
Hypercom and the Hypercom Logo are registered trademarks of Hypercom Corporation. The Integrated Enterprise Network is a trademark. This publication is proprietary to Hypercom Corporation and is intended solely for the contractual use of Hypercom customers. This publication may not be reproduced or distributed for any purpose without the written permission of Hypercom Corporation.
NOTICE
Hypercom Corporation reserves the right to make changes to specifications at any time and without notice. The information furnished in this publication by Hypercom Corporation is believed to be accurate and reliable, however, no responsibility is assumed by Hypercom Corporation for its use.
This document applies to the Hypercom Integrated Enterprise Network system and supporting software.
FCC NOTICE
The Hypercom devices described herein generate and use radio frequency energy. If not installed and used properly, they may interfere with radio and television reception.
These devices have been tested and certified to comply with the limits for a Class A digital device, as defined in Part 15 of the Federal Communications Commission (FCC) rules. Class A limits are designed to provide reasonable protection against radio/television interference in a business environment.
To comply with FCC regulations, you must use shielded cables with these devices. Operation with unapproved equipment or unshielded cables is likely to result in interference with radio or television reception. Changes made to these devices without the approval of Hypercom Corporation could void your authority to operate them.
These devices may cause interference even though they meet Class A limits. If there is interference, try to eliminate it by:
■ Reorienting or relocating the receiving antenna of the radio or television. ■ Increasing the distance between the receiver and the Hypercom equipment.
■ Connecting the device to an outlet on a circuit different from that to which the receiver is connected.
These devices have also been tested and certified to comply with Part 68 of the FCC rules. FCC Part 68 requires that you:
■ Provide the FCC registration number of the devices (identified on the device itself) to the telephone
company, if requested;
■ Establish that the sum of Ringer Equivalence Numbers of all devices connected to a single telephone
line does not exceed five for reliable operation;
■ Not install this device on coin operated or party telephone lines.
Repair work on these devices must be done only by Hypercom Corporation or a Hypercom authorized repair station.
Ta b l e o f C o n t e n t s
CHAPTER 1 I
NTRODUCTION. . . 1-1
Objective . . . 1-2 Terminology. . . 1-2 The IEN Design Process . . . 1-4CHAPTER 2 N
ETWORKR
EQUIREMENTSANDD
EFINITIONS. . . 2-1
Network Design Considerations . . . 2-2 Gathering Network Requirements . . . 2-2 Node Classifications . . . 2-3 Assigning the Regional and Remote Nodes . . . 2-4CHAPTER 3 WAN T
OPOLOGYS
ELECTION. . . 3-1
Defining the WAN Topology . . . 3-2 HDLC . . . 3-3 X.25 . . . 3-4 Frame Relay . . . 3-5 WAN Physical Interfaces . . . 3-8 Determining the WAN Topology . . . 3-9 Identifying Network Communication Points. . . 3-10
CHAPTER 4 P
ORTP
ROCESSORANDM
ODULES
ELECTION. . . 4-1
Selecting Port Processors and Modules. . . 4-2 Creating A Network Map. . . 4-2
Selecting Port Processor Software . . . 6-2 Defining WAN Port Processor Software Requirements . . . 6-2 HDLC WAN Port Processor Software Matrix . . . 6-3 Frame Relay WAN Port Processor Software Matrix . . . 6-4 Dial Backup Port Processor Software Matrix . . . 6-5 T1/E1 WAN Interface Port Processor Software Matrix . . . 6-6 X.25 Port Processor Software Matrix . . . 6-7 Defining Local Port Processor Software Requirements . . . 6-8 Asynchronous Port Processor Software Matrix . . . 6-9 Bisynchronous Port Processor Software Matrix . . . 6-10 Burroughs Poll/Select Port Processor Software Matrix . . . 6-11 Bus Extension Port Processor Software Matrix . . . 6-12 Ethernet Port Processor Software Matrix . . . 6-13 Gateway Port Processor Software Matrix . . . 6-14 IENView Access Port Processor Software Matrix . . . 6-16 SDLC Port Processor Software Matrix. . . 6-17 Token Ring Port Processor Software Matrix. . . 6-18 User Services Port Processor Software Matrix . . . 6-19 Voice Port Processor Software Matrix . . . 6-21
CHAPTER 6 C
HASSISS
ELECTION. . . 5-1
Selecting the Chassis. . . 5-2 When to Use the IEN 100. . . 5-2 When to Use the IEN 500. . . 5-2 When to Use the IEN 2000. . . 5-3 When to Use the IEN 2500. . . 5-3 When to Use the IEN 4000. . . 5-3 When to Use the IEN 5000. . . 5-4 When to Use the IEN 6000. . . 5-4CHAPTER 7 C
ABLEANDA
DAPTORS
ELECTION. . . 7-1
Cables and Adaptors . . . 7-2 Defining the Required Cables and Adaptors . . . 7-2 Determining the Required Cables and Adaptors . . . 7-2 General Hardware Information . . . 7-3
C h a p t e r 1
I n t r o d u c t i o n
The Integrated Enterprise Network™ (IEN) Product Design Reference can assist you in selecting the appropriate products for designing a network. This guide provides information about the IEN design process and its basic components.
O
BJECTIVE
The guide takes you through the product selection process for designing a network. The configuration diagrams in the IEN Product Design Reference illustrate commonly used protocols, interfaces, and design strategies.
T
ERMINOLOGY
The following terms are used throughout this reference. For more detailed definitions, refer to the IEN Technical Glossary.
Central Node The uppermost node in the Hypercom IENView™ network
management system through which IENView can administer and view all other nodes. The central node is usually the primary node
connected to IENView.
Logical Node A logical concept defined only within IENView. The logical node represents the frame relay cloud with its uplink and downlink IDs. For example: The logical node, or frame relay cloud, on the Hypercom IENView network map lists all the frame relay connection IDs associated with that logical node.
Node One or more bus-extended or expanded IEN chassis, comprised of up to 240 bus addresses.
Node ID A unique number assigned to each node within an IEN network. It is the remote ID number assigned when you create the database. Port A single physical interface associated with its own bus address. Port Processor Refers to a self-contained CPU/interface circuit board that
incorporates all necessary circuitry to communicate with the IEN chassis busses. The port processor contains all memory to run the CPU independently. Hypercom produces a number of different types of port processors that are capable of handling single or multiple functions.
Regional Node A node within the Hypercom IENView network management system that does not function as a central node; it functions as a concentrator for subordinate nodes. From a regional node, you can view the regional node and subordinate nodes. You can also administer these nodes if IENView is connected to the regional node.
Remote Node A node within the Hypercom IENView network management system that has no subordinates. From a remote node, you can only view the remote node. You can administer the remote node if IENView is connected to the remote node.
Slot A physical location where a port processor is inserted into an IEN chassis.
Slot Connector A physical connector located on the rear of an IEN chassis. Slot Connector
Number
A unique number assigned to each slot on the rear of an IEN chassis.
T
HE
IEN D
ESIGN
P
ROCESS
The IEN design process contains six steps. Each step in this process equates to a chapter in this reference, as follows:
Network Requirements and Definitions
Chapter 2 describes the process for gathering requirements. This information is necessary for selecting the correct products for design implementation.
WAN Topology Selection
Chapter 3 describes the WAN topologies available within the Integrated Enterprise Network.
Port Processor and Module Selection
Chapter 4 describes how to select port processors and modules for the protocols, applications, and interfaces within the network.
Port Processor Software Selection
Chapter 5 describes the applications available within the Integrated Enterprise Network. This chapter includes how to select port processor software for the network design.
Chassis Selection
Chapter 6 describes the IEN chassis and when to use a particular IEN chassis within the network.
Cable and Adaptor Selection
Chapter 7 describes how to select the correct cables and adapters to gain connectivity. This chapter includes a cable matrix, listing the selections for each port processors by function.
C H A P T E R 2
N e t w o r k Re q u i r e m e n t s
a n d D e f i n i t i o n s
The first step in the Integrated Enterprise Network design process is to determine all network requirements and their functions within each site. This includes identifying all the protocols, applications, and interfaces required at each site. You can classify each site within the IEN system with this information. Topics include:
■ Network Design Considerations ■ Gathering Network Requirements ■ Assigning Node Classifications
N
ETWORK
D
ESIGN
C
ONSIDERATIONS
When you design a network, you must consider basic site factors and information. The factors to consider include:
■ Site functions
■ Protocols and interfaces ■ Equipment
■ Existing and desired WAN topology ■ Existing and desired LAN topology ■ Physical space
■ Environment ■ Power
■ Demarcation points
Within this process, you gather information about what the network currently supports and the types of information and speeds that you want the network to support in the future.
Gathering Network Requirements
Through the requirements-gathering process, you obtain information on all sites included in the network analysis. You use this information to classify the sites in the network.
Within an IEN, sites are labelled as nodes. You can classify nodes as central, regional, or remote; only one node is classified as the central, but multiple nodes can be classified as regional or remote. The functions performed at each site determine the network hierarchy. Each IEN node consists of one or more bus-extended or expanded IEN chassis, containing up to 240 bus addresses.
Node Classifications
The central node is the uppermost node in the network. The central node usually contains the hosts that manage the processing for the rest of the network. It may also contain functions that are within a corporate office or data processing center, including accounting and transaction processing. You usually connect IENView to the central node, because you can view and administer the entire network from the central node.
A regional node is usually a concentrator for remote nodes within the network. Typical sites that qualify to be regional nodes include warehouses and large bank branches in major areas. The regional node strategy is effective when there are many remote nodes within close proximity that require connection to the central node. When you use a regional node, you can concentrate the traffic from remote nodes and send it through one connection. From a regional node, you can view the regional node and remote nodes within its region. You can also administer these nodes if you connect IENView to the regional node.
A remote node is the lowest node in the structure. A remote node does not have any nodes that are subordinate to it in the network. Typical sites that you can classify as remote nodes include a small bank branch or a local sales office.
From the information gained while gathering requirements, you can begin to assign node classifications to locations within the network.
Assigning the Regional and Remote Nodes
In the current network design as shown in Figure 2-1, the warehouses and sales offices are classified as remote nodes, each one having access to the corporate office or the central
node. The current network design is not efficient. It does not provide easy traffic flow or low communications costs because:
■ All the local sales offices require access to New York
■ The state sales offices require access to the file server at the state’s warehouse
To reduce traffic flow through the corporate office in New York, promote the warehouses to
regional nodes to concentrate the traffic from the state’s sales offices and to provide a direct route to the central node in New York.
Figure 2-2 Promoting warehouses from remote to regional nodes
CURRENT NETWORK STRUCTURE
C H A P T E R 3
WA N To p ol og y Se l ec t i o n
The chapter describes the supported WAN topologies for an IEN. Topics include:
■ Defining the WAN Topologies ■ Determining the WAN Topology
D
EFINING
THE
WAN T
OPOLOGY
Within an Integrated Enterprise Network, you can select from three WAN topologies:
■ HDLC ■ X.25
■ Frame Relay
Select a topology based on the speeds, protocols, and interfaces requiring support and the amount of traffic within your current network. Consider the existing WAN services and how to use those services effectively within your new design.
HDLC
IEN nodes can connect using an HDLC LAP-B point-to-point or multiple point-to-point backbone over a private leased-line network, providing a low-overhead WAN backbone. You can use HDLC links with other WAN topologies such as frame relay, tail circuits from regional nodes, or consolidation links from regional to central nodes. An HDLC multiple point-to-point backbone supports up to eight drops.
Figure 3-1 HDLC multiple point-to-point backbone topology
An HDLC point-to-point backbone corresponds to the number of nodes and leased lines available in the network.
X.25
IEN nodes can also connect using an X.25 backbone network. Each IEN X.25 backbone connection supports switched virtual circuit (SVC) connections, permanent virtual circuit (PVC) connections, or network management loading of SVC or PVC call address tables. An X.25 backbone allows connection of up to 64 IEN nodes.
Figure 3-3 IEN X.25 backbone topology
You can also combine X.25 with HDLC as a backbone infrastructure.
Frame Relay
IEN nodes can also connect using a frame relay backbone. This backbone supports the transport of legacy and LAN-based protocols and also allows voice and data to travel over the same backbone. Frame relay provides predictable network transition times and routing between network nodes. There are various frame relay backbones available.
Using frame relay as a backbone, you can route IEN data traffic from any node to any other node. This backbone topology can support up to 240 PVCs per port.
You can route LAN traffic using RFC1294 or RFC1490 to non-IEN routers.
Figure 3-6 Frame relay RFC1490 backbone topology
You can route SNA/SDLC LLC2 traffic to host FEPs such as the 3745.
Using the Frame Relay Network-to-Network (NNI) interface, you can pass frame relay traffic from local ports to the frame relay network. This is known as Frame Relay Pass-Through.
Figure 3-8 Frame Relay Pass-Through backbone topology
A carrier-based frame relayconnection may often be the best choice when long distances are involved. Carrier-based frame relay requires only a local access circuit from your location to the carrier’s local premises. The carrier’s internal network structure covers the long distance. A local-access circuit is then made between a remote, regional, or central node and the carrier’s local premises. A carrier-based frame relay may reduce costs compared to a dedicated circuit.
WAN Physical Interfaces
IEN supports a direct digital service (DDS) and T1 WAN connections, as well as V.35 and ISDN.
T1 or Fractional T1 (FT1)
T1 may often be the best WAN interface when the network requires high bandwidth applications between two nodes or among larger numbers of outside, or non-tie-line, voice lines. Cost savings come from the volume discount a carrier can offer compared to
individually connected lines. Any more than one 64Kbps connection is considered a T1 connection. Two to twenty-four of these connections are considered a fractional T1.
56K/64Kbps DDS
A 56/64Kbps DDS connection may be best suited for lower bandwidth applications. Small numbers of 56K/64K DDS circuits may often result in lower cost than a fractional T1 or full T1 connection. The threshold for selecting an FT1 or a T1 connection varies by carrier.
D
ETERMINING
THE
WAN T
OPOLOGY
To define the WAN requirements, build from the lowest level to the highest, or from the remote nodes to the central node. As you define bandwidth requirements, you can determine the bandwidth needed for growth and how much bandwidth the central node requires to support all its subordinate nodes.
Figure 3-9 Sample network diagram
The sample network diagram incorporates both point-to-point and multiple point-to-point connections. Between the remote nodes and respective regional nodes is a frame relay cloud using multiple point-to-point connections. The regional nodes connect to the central node through point-to-point connections.
Identifying Network Communication Points
A network communication point is where two nodes intersect for transport. Based on the network diagram on the previous page, the network communication points are:
■ The remote nodes to the frame relay cloud (A). ■ The frame relay cloud to the regional node (B). ■ The regional nodes to the central node (C).
Figure 3-10 Network communications points
Using the sample network diagram as an example, the remote nodes (A) require access to frame relay. A 64Kbps DDS is considered sufficient for the expected traffic volumes for the communications.
Each remote node also requires a Committed Information Rate (CIR) of 19.2Kbps because of the bursting nature and volumes expected. Each remote node has a permanent virtual circuit (PVC) defined in the frame relay network to the regional node.
Figure 3-11 Remote nodes WAN bandwidth requirements
The regional nodes (B) require access to frame relay and to each remote node in their region. Selecting a fractional T1 (FT1) with 128K, or two DS0s, of bandwidth available enables the future addition of remote nodes to the frame relay network.
The central node (C) uses a T1 to handle the volumes expected from the combination of LAN traffic and future remote expansion.
C H A P T E R 4
Por t Pr o c e s s o r a n d M o d u l e
Se l ec t i o n
The chapter describes how to select port processors and modules for a network configuration. Topics include:
■ Creating a Network Map
■ Determining the WAN Port Processors and Modules
S
ELECTING
P
ORT
P
ROCESSORS
AND
M
ODULES
Certain protocols require a specific port processor and module; other protocols have multiple port processor and module combinations. Each of the multiple port processor options is based on specific network design requirements, such as WAN interface and WAN speed.
Creating A Network Map
Using the information gathered in the network requirements process and the network topology diagram, you can create a network map. To create a network map, use the functional information for the central, regional, and remote nodes to identify the protocol and interface requirements for each node.
The information on the network map helps identify the required port processors and modules. Within the network, you specify WAN requirements and the node-level, or local, requirements. The number and type of port processors and modules required for each WAN and local node helps determine chassis requirements for each node.
Defining WAN Port Processors and Modules
The WAN protocols and applications include:■ Dial backup ■ Frame relay ■ HDLC ■ ISDN
■ Voice over frame relay ■ X.25
As shown in Table 4-1, some protocols require a specific port processor and module; others require a flowchart to identify the correct port processor and module. The flowcharts use specific parameters, such as physical interface requirements and line speed, to determine the appropriate port processor. Each port processor requires one slot in a chassis.
Table 4-1 WAN port processor protocols and applications Protocol/application Port processor
Dial backup See Figure 4-2 on Page 4-4.
Frame relay See Figure 4-3 on Page 4-5.
HDLC IEN to IEN WAN See Figure 4-4 on Page 4-6.
ISDN BRI CID63 with ISD01-U or ISD01-ST.
ISDN PRI DTC11-LHO plus CID61 x N (Each CID61 supports three
Dial Backup Flowchart
Use the Dial Backup flowchart to determine the port processor and module requirements when you implement dial backup applications for a network.
Frame Relay WAN Protocol Flowchart
Use the Frame Relay WAN Protocol flowchart to determine the port processor requirements when you implement a frame relay WAN backbone.
HDLC WAN Protocol Flowchart
Use the HDLC WAN Protocol flowchart to determine the port processor requirements when you implement an HDLC IEN to IEN WAN backbone.
Figure 4-4 HDLC WAN Protocol flowchart HDLC WAN
WAN Interface?
Add CID61 and DTC11-LHO
Add CID63 with DSU63 END Greater than 128Kbps? Add CID63 Interface? Internal DSU? Add External DSU/
CSU
Add CIV01 Add CIR01
56/64K DDS V.35 No No RS232 T1 Yes Add CID61 Yes V.35
Voice Over Frame Relay Protocol Flowchart
Use the Voice Over Frame Relay Protocol flowchart to determine the port processor
requirements when you implement voice over frame relay backbone. Each CID61 supports one DVF18 module. The DVF18 can support two, four, or eight compressed voice channels.
F/R with Voice WAN Interface? Add DTC11-LHO 128Kbps or Less ? Yes No Add External DSU
or CSU
Add CID61 with DSU01
Add Dedicated CID61 for WAN
Add CID61 with DVF18-X
END T1
Defining Local Port Processors and Modules
The local protocols and applications include:
■ Async ■ Bisync ■ Ethernet ■ HDLC ■ IENView ■ PBX/key system ■ SDLC ■ Token ring ■ X.25
As shown in Table 4-2, some protocols require a specific port processor and module and others require a flowchart to identify the correct port processor and module. The flowcharts use specific parameters, such as physical interface requirements and line speed, to
determine the appropriate port processor. Each port processor requires one slot in a chassis.
Table 4-2 Local port processor protocols and applications Protocol/application Port processor
Async CID63 with CIR01.
Bisync CID63 with CIR01 (or CIV01).
Ethernet LET61 (LET61H if located in the central node).
HDLC local port See Figure 4-6 on Page 4-9.
IENView connection See Figure 4-7 on Page 4-10.
PBX/key system See Figure 4-8 on Page 4-11.
SDLC CID63 with CIV01 (or CIR01).
Token ring LTR61 (LTR61H if located in the central node).
HDLC User Port Protocol Flowchart
Use the HDLC User Port Protocol flowchart to determine the port processor requirements when you implement the HDLC local port protocol into your network.
IENView Connection Flowchart
Use the IENView Connection Interface flowchart to determine the port processor
requirements when determining which IENView connection is best suited for your network.
PBX/Key System Interface Flowchart
Use the PBX/Key System Interface flowchart to determine the port processor requirements when the network contains a PBX or a key system configuration. The DLA14 port processor supports two channels in four-wire E&M mode and four channels in two-wire FXO or FXS mode. Select the number of DLA14s that corresponds to the number of channels in the network design.
C H A P T E R 5
Por t Pro c e s s o r S o ft w a re
Se l ec t i o n
This chapter describes the available port processor software. Topics include:
n Defining the Port Processor Software Requirements n Determining the Port Processor Software Usage
S
ELECTING
P
ORT
P
ROCESSOR
S
OFTWARE
The next step in the network product design is to determine the software required for each port processor. To identify the appropriate software for the network, use the software matrices and descriptions in this chapter.
The selection process for the port processor software divides into WAN and local
requirements. Start with the WAN interface requirements at the central node and work down to the remote nodes. A software defined for a central node may require a partner software running at a remote node.
Defining WAN Port Processor Software Requirements
The WAN software matrices include:n HDLC WAN n Frame relay WAN n Dial backup
n T1/E1 WAN Interface n X.25
Included with the matrix is a brief description of port processor software use in a network. For more detailed information, refer to the individual software descriptions or the IEN Software Reference.
HDLC WAN Port Processor Software Matrix
Use the HDLC WAN Port Processor Software Matrix to determine the port processor software requirements when using this WAN for the network.
HDLC WAN Software Descriptions
The HDLC WAN software in the matrix performs the following functions:
n C5HNHNN, C61NHNN, and CLMNHNN provide node-to-node
communications using the HDLC/LAPB protocol.
n C5HNHNP provides primary, multipoint node-to-node communications using
HDLC/NRM protocol.
n C5HNHNS provides secondary, multipoint, node-to-node communications
using HDLC/NRM protocol.
n C61NHDE provides encrypted node-to-node communications using HDLC/
LAPB protocol.
Table 5-1 HDLC WAN Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C5HNHNN l l l C5HNHNP C5HNHNS C61NHDE l C61NHNN l CLMNHNN l
Frame Relay WAN Port Processor Software Matrix
Use the Frame Relay WAN Port Processor Software Matrix to determine the port processor software requirements when using this WAN for the network.
Frame Relay WAN Software Descriptions
The Frame Relay WAN software in the matrix performs the following functions:
n C61NHFX and CLMNHFX provides node-to-node communications using a
frame relay network.
n C61NHFV provides node-to-node communications using a frame relay
network including voice compression applications.
Table 5-2 Frame Relay WAN Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C61NHFX l
C61NHFV l
Dial Backup Port Processor Software Matrix
Use the Dial Backup Port Processor Software Matrix to determine the port processor software requirements when using dial backup applications for the network.
Dial Backup Software Descriptions
The Dial Backup software in the matrix performs the following functions:
n C5HNHDB, C61NHDB, and C63NHDB provide a backup path for the primary
node-to-node, frame relay, or HDLC/NRM connection.
n C61NIPB supports the HDLC/LAPB protocol for node-to-node communications
on three ISDN B channels.
n C61NIPD contains the LAPD/Q.931 protocol for communicating to the user or
network interface of an ISDN network.
n C63NHIB supports the ISDN BRI 1B+D functionality in an uplink, regional, or
central node.
n C63NHI2 supports incoming calls from one or two uplink, regional, or remote
nodes.
Table 5-3 Dial Backup Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C5HNHDB l l C61NHDB l C63NHDB l C61NIPB l C61NIPD l C63NHIB l C63NHI2 l
T1/E1 WAN Interface Port Processor Software Matrix
Use the T1/E1 WAN Interface Port Processor Software Matrix to determine the port processor software requirements when using a T1 or E1 interface for the network.T1/E1 WAN Interface Software Descriptions
The T1/E1 WAN Interface software in the matrix performs the following functions:
n D11NAFT and D11NASW provide control for the DTC11 T1 interface port
processor in the node.
n E11NASW provides control for the DTC11-E1 interface port processor in the
node.
Table 5-4 T1/E1 WAN Interface Port Processor Software Matrix
Software name Port processors DTC11-LHO DTC11-E1 DSX11 D11NAFT l D11NASW l E11NASW l
X.25 Port Processor Software Matrix
Use the X.25 Port Processor Software Matrix to determine the port processor software requirements when using this WAN for the network.
X.25 Software Descriptions
The X.25 software shown in the matrix, C5ZHNPNN and C61NPNN, both provide an interface to a public or private X.25 network for interconnection to a node.
Table 5-5 X.25 WAN Port Processor Software Matrix
Software name
Port processors
CID15H CID61 CID63
C5HNPNN l
Defining Local Port Processor Software Requirements
When you finish defining the WAN software, start defining the local port processor, or user services, software. Start with the central node and work down toward the remote. A software defined in the central node usually requires a companion software defined in a remote node.The Local software matrices include:
n Async n Bisync n Burroughs Poll/Select n Bus extension n Ethernet n Gateways n IENView access n SDLC n Token Ring n User services n Voice
Included with the matrix is a brief description of port processor software use in a network. For more detailed information, refer to the individual software descriptions or the IEN Software Reference.
Asynchronous Port Processor Software Matrix
Use the Async Port Processor Software Matrix to determine the port processor software requirements when using this protocol for the network.
Asynchronous Software Descriptions
The asynchronous software in the matrix performs the following functions:
n C5HNAIP polls ATM or teller controllers configured for an asynchronously
polled operation.
n C5HNAIS accepts polling/select sequences from a host port and forwards
information to C5HNAIP in a remote node.
n C5HNASP provides a primary transparent, polled interface to a remote device
supporting an asynchronous protocol.
n C5HNASS provides a secondary transparent, polled interface to a host port
supporting an asynchronous protocol.
n C5HNATP provides a primary, transparent interface to a remote device
supporting an asynchronous protocol.
n C5HNATS provides a secondary, transparent interface to a host connection
supporting an asynchronous protocol.
n CLMNATS provides either a primary or secondary transparent interface to a
central or remote device supporting an asynchronous protocol.
Table 5-6 Asynchronous Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C5HNAIP l l C5HNAIS l l C5HNASP l l C5HNASS l l C5HNATP l l C5HNATS l l CLMNATS l
Bisynchronous Port Processor Software Matrix
Use the Bisync Port Processor Software Matrix to determine the port processor software requirements when using this protocol for the network.
Bisynchronous Software Descriptions
The bisynchronous software in the matrix performs the following functions:
n C5HNBTP provides an interface to a remote device configured as a 3270
bisync secondary controller or a 2780/3780 remote station.
n C5HNBTS provides an interface to a host serial interface configured as a 3270
bisynchronous primary or supporting 2780/3780 communications protocol.
n CLMNBSC provides primary and secondary bisync driver functions and routes
bisync data to a remote bisync primary driver.
Table 5-7 Bisynchronous Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C5HNBTP ● ● ●
C5HNBTS ● ● ●
Burroughs Poll/Select Port Processor Software Matrix
Use the Burroughs Poll/Select Port Processor Software Matrix to determine the port processor software requirements when using this protocol for the network.
Burroughs Poll/Select Software Descriptions
The Burroughs Poll/Select software in the matrix performs the following functions:
n C5HNBDP polls automatic teller machines (ATM) or teller controllers through
an asynchronous interface.
n C5HNBDS receives polls from a host port and forwards information to
C5HNBDP to acquire the poll addresses necessary to poll remote ATM or teller controllers.
n C5HNBBP polls ATM or teller controllers through a bisychronous interface. n C5HNBBS receives polls from a host port to pass to C5HNBBP.
n CLMNBUR provides a Burroughs P/S connection to a host and remote device.
Table 5-8 Burroughs Poll/Select Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C5HNBDP ● ●
C5HNBDS ● ●
C5HNBBP ● ● ●
C5HNBBS ● ● ●
Bus Extension Port Processor Software Matrix
Use the Bus Extension Port Processor Software Matrix to determine the port processor software requirements when using this application for the network.
Bus Extension Software Descriptions
The Bus Extension software in the matrix performs the following functions:
n E61NEEX allows the chassis to be interconnected for supporting up to 240 ports
in one IEN node using an Ethernet interface.
n T61NTEX allows the chassis to be interconnected for supporting up to 240 ports
in one IEN node using a Token Ring interface.
Table 5-9 Bus Extension Port Processor Software Matrix
Software name
Port processors
LET61 LET61B LET61H LTR61 LTR61B LTR61H
E61NEEX l
Ethernet Port Processor Software Matrix
Use the Ethernet Port Processor Software Matrix to determine the port processor software requirements when using this protocol for the network.
Ethernet Software Descriptions
The E61NEMX Ethernet software provides an interface to Ethernet LAN segments functioning as multiprotocol routers or bridges to remote subnets reachable through the WAN
connection or other external routers.
Table 5-10 Ethernet Port Processor Software Matrix
Software name
Port processors
LET61 LET61B LET61H LTR61 LTR61B LTR61H
Gateway Port Processor Software Matrix
Use the Gateway Port Processor Software Matrix to determine the port processor software requirements when using this application for the network.
Table 5-11 Gateway Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C5HNAAT l l l C5HNB72 l l l C5HNB7T l l l C5HNBS2 l l C5HNBT2 l l C5HNBST l l l C5HNBTT l l l C63NB7T l C63NBST l C63NBTT l C5HNABT l l l C5HNBBT l l l C5HNST2 l l l C5HNSST l l l C63NS0T l C63NSPT l C5HNPTC l l l
Gateway Software Descriptions
The Gateway software in the matrix performs the following functions:
n C5HNAAT polls a TCP/IP host configured for an asynchronously polled
operation.
n C5HNB72, C5HNB7T, and C63NB7T provide a synchronous interface
supporting 3780 point-to-point bisync protocol to a bisync device.
n C5HNBS2, C5HNBT2, C5HNBST, C5HNBTT, C63NBST, and C63NBTT provide
an interface to a remote device configured as a 3270 bisync protocol driver.
n C5HNABT provides an interface to end devices configured as Burroughs
primary asynchronous control units.
n C5HNBBT provides an interface to end devices configured as Burroughs
secondary bisynchronous control units.
n C5HNST2 provides a synchronous interface supporting SNA LU2 protocol to an
SDLC device.
n C5HNSST provides a synchronous interface supporting SNA 3601 protocol to
an SDLC device.
n C63NS0T provides an SNA /SDLC NCP interface for transparent networks. n C63NSPT provides an SNA /SDLC NCP interface for transparent networks and
supports SNA LU0 secondary, SNA LU2 secondary, and SDLC secondary.
n C5HNPTC and C63NPTT provide a synchronous interface supporting X.25
protocol to an X.25 device.
n C61NSL2 and CLMNSL2 provide a serial interface to support devices requiring
SNA/SDLC data streams to be converted to LLC2 data frames.
n C63NSTQ provides a serial interface to support devices requiring SNA/SDLC
IENView Access Port Processor Software Matrix
Use the IENView Access Port Processor Software Matrix to determine the port processor software requirements when using this application for the network.
IENView Access Software Descriptions
The IENView Access software shown in the matrix, C5HNAPC and CLMNAPC, both connect an IENView platform, typically a PC, to a central IEN node.
Table 5-12 IENView Access Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C5HNAPC l l l
SDLC Port Processor Software Matrix
Use the SDLC Port Processor Software Matrix to determine the port processor software requirements when using this protocol for the network.
SDLC Software Descriptions
The SDLC software in the matrix performs the following functions:
n C53NSTP, C61NSTP, and CLMNSTP provide a primary serial interface to
support devices using SDLC SNA/SDLC data streams.
n C5HNSTS, C61NSTS, and CLMNSTS provide a secondary, serial interface to an
FEP port requiring support for SNA/SDLC data streams.
Table 5-13 SDLC Port Processor Software Matrix
Software name
Port processors
CID15 CID15H CID15HA CID61 CID63
C53NSTP ● ● ● C5HNSTS ● ● ● C61NSTP ● C61NSTS ● CLMNSTP ● CLMNSTS ●
Token Ring Port Processor Software Matrix
Use the Token Ring Port Processor Software Matrix to determine the port processor software requirements when using this protocol for the network.
Token Ring Software Descriptions
The T61NTMX Token Ring software provides an interface to Token Ring LAN segments functioning as multiprotocol routers or bridges to remote subnets reachable through the WAN connection or other external routers.
Table 5-14 Token Ring Port Processor Software Matrix
Software name
Port processors
LET61 LET61B LET61H LTR61 LTR61B LTR61H
User Services Port Processor Software Matrix
Use the User Services Port Processor Software Matrix to determine the port processor software requirements when using this application for the network.
Table 5-15 User Services Port Processor Software Matrix
Software name
Port processors
LET61 CID15H CID15HA CID61 CID63
C61NPTP l C61NPTS l C61NHFS l C5HNAX3 l l C5HNPX3 l l C63NXPA l CLMNPSW l CLMNPPP l CLMNLAT l E61NELT l
User Services Software Descriptions
The User Services software in the matrix performs the following functions:
n C61NPTP provides an interface to a remote serial connection supporting an
HDLC/LAPB (X.25) or SDLC (PU.T4) primary device.
n C61NPTS provides an interface to a central serial connection supporting an
HDLC/LAPB (X.25) or SDLC (PU.T4) secondary device.
n C61NHFS connects a non-IEN FRAD directly to a co-located remote node to
provide pass-through services.
n C5HNAX3 and C63NXPA provide a transparent asynchronous interface to a
remote device supporting an asynchronous protocol.
n C5HNPX3 provides a serial interface to a host connection supporting X.25. n CLMNPSW provides an X.25 primary or secondary interface to an IEN network. n CLMNPPP allows serial-attached PCs to access an IP network through IEN
routing.
n CLMNLAT and E61NELT provide a device and server interface for LAT version
Voice Port Processor Software Matrix
Use the Voice Port Processor Software Matrix to determine the port processor software requirements when using this application for the network.
Voice Software Descriptions
The Voice software in the matrix performs the following functions:
n C61NHFV supports packetized voice over frame relay or point-to-point links
and voice compression and call control.
n DL4NVFR provides a four-channel analog line interface for connections to an
IEN chassis.
n D11NAVD provides control for the DTC11 T1 interface port processor and
allows the passage of voice traffic across the network.
n DSXNAVD provides control for the DSX11 T1 interface port processor and
allows for the passage of voice traffic to a PBX connection.
n E11NAVD provides control for the DTC11-E1 interface port processor and
allows the passage of voice traffic across the network and to a PBX connection.
Table 5-16Voice Port Processor Software Matrix
Software name
Port processors
CID61 DLA14 DSX11 DTC11-E1 DTC11-LHO
C61NHFV l
DL4NVFR l
D11NAVD l
DSXNAVD l
C H A P T E R 6
C h a s s i s S e l e c t i o n
This chapter describes the available IEN chassis. Topics include:
■ Defining the Chassis
S
ELECTING
THE
C
HASSIS
Within the IEN product family, there are seven different chassis that you can use to build your node.
The two factors used to determine the chassis for a specific node are the node protocols and applications and the number of port processors required for the node.
When to Use the IEN 100
A dial operation chassis, the IEN 100 is designed to connect an automatic teller machine (ATM) to a host.
Because the IEN 100 is only a specialized remote node device, compare the port processor requirements of each remote node to determine whether an IEN 100 meets the
requirements for the remote node.
When to Use the IEN 500
A one-slot chassis, the IEN 500 is designed to function as a highly-flexible, remote node device for smaller remote offices. The IEN 500 uses the CID63 port processor to provide up to three ports for configuring various WAN, LAN, and legacy applications.
Table 6-1 IEN chassis
Chassis Central Regional Remote
IEN 100 No No Yes
IEN 500 No No Yes
IEN 2000 No No Yes
IEN 2500 No No Yes
IEN 4000 No Yes Yes
IEN 5000 Yes Yes Yes
Because the IEN 500 is only a remote node device, compare the port processor requirements of each remote node to determine whether an IEN 500 meets the requirements for the remote node.
When to Use the IEN 2000
A two-slot chassis, the IEN 2000 is designed for pay-as-you-grow flexibility. It is expandable to four chassis for a total capacity of eight slots. When bus-connected with two or more IEN 2000s, the power bus is shared, offering dual, load-sharing power. The IEN 2000 offers a versatile solution to the requirements of the remote office environment.
Because the IEN 2000 is only a remote node device, compare the port processor
requirements of each remote node to determine whether one IEN 2000 or multiple-linked IEN 2000s meet the requirements for the remote node.
When to Use the IEN 2500
A four-slot chassis, the IEN 2500 is capable of running multiple port processors. The IEN 2500 chassis is typically used at a remote node providing support for four port processors. The chassis can be bus-connected to an additional IEN 2500 chassis for an eight-slot chassis configuration. This allows for expansion as new requirements develop.
Because the IEN 2500 is only a remote node device, compare the port processor
requirements of each remote node to determine whether one IEN 2500 or multiple-linked IEN 2500s meet the requirements for the remote node.
When to Use the IEN 4000
An eight-slot chassis, the IEN 4000 can function as a regional concentrator or as the solution for larger remote nodes with the greatest bandwidth needs and the widest mix of applications.
When to Use the IEN 5000
A sixteen-slot chassis, the IEN 5000 is designed to be used at the central, regional, and remote nodes. This stackable chassis is bus extendable to support multiple remote nodes. Compare the port processor requirements of each remote and regional node to determine whether one IEN 5000 or multiple-linked IEN 5000s meet the requirements for the nodes.
When to Use the IEN 6000
A sixteen-slot chassis, the IEN 6000 is designed to be used as a central or regional node. This stackable chassis is bus extendable to support multiple remote nodes.
Compare the port processor requirements of each remote and regional node to determine whether one IEN 6000 or multiple-linked IEN 6000s meet the requirements for the nodes.
C H A P T E R 7
C a b l e a n d A d a p t o r
Se l ec t i o n
The chapter describes the cable and adaptor option requirements. Topics include:
■ Defining the Required Cables and Adaptors ■ Determining the Required Cables and Adaptors ■ General Hardware Information
C
ABLES
AND
A
DAPTORS
Identification of the cables and adapters is the final network design requirement. If you know the port processor function within the network, you can identify the cable and adapter requirements to gain connectivity.
Defining the Required Cables and Adaptors
Selecting appropriate cables and adaptors depends on the physical interface specifications at each network node. Listed in this chapter are the available cables for each type of port processor. The packing list and the installation package also provide the appropriate cable and adaptor information for each customer node. Each cable and adapter is clearly marked with its information type.
Use the cables to connect IEN products to customer-provided connections. Most of the cables are not directly connected to customer equipment, but to customer-provided cables. Note cable genders and adjust connections accordingly.
Determining the Required Cables and Adaptors
To select the appropriate cable, locate the port processor or chassis in the Port Processor/ Chassis column. Read down the left hand side of the matrix to locate the desired physical interface and function.
The intersecting cell between the port processor or chassis and physical interface identifies the appropriate cable or adaptor. If a cell does not contain a cable or adaptor, the configuration is not correct. Review the port processor’s function and physical interface requirements and repeat the process.
General Hardware Information
The following is a list of general IEN hardware information:
■ The CID63 port processor requires either a Type T(63) cable for a RJ11
connection or a Type Y(63) cable for a DB25 connection.
■ The Type T(63) and Type Y(63) cables also require additional cables to
complete connectivity to customer devices.
■ DIP Switches on the Type Y(63) cable determine if the interface is RS232 or
V.35.
■ The Type Y(63) and Type T(63) cables are included with the purchase of the
CID63 port processor.
■ When using the DB25 connector for RS232, the connector is DTE. To perform
as a DCE, use the appropriate crossover cable.
■ The Type VM connects a maintenance modem when using an external CSU/
Table 7-1 Port processor cable requirements
Port processor
CID15H CID15H-A CID61 CID61-DUAL CIM15H-22B CIM15H-33
C o nnec ti o n Int e rfa ce Dev ic e V.35 DTE + RS232 DTE Analog Voice 4 x RJ11 Punch-down RS232
IEN to DTE Type D (M to F) Type D6 (M to F) Type D (M to F) Type D (M to F) IEN to DCE Type A
(M to F) Type A (M to F) Type A (M to F) Type A (M to F) RS232 X 3
IEN to DTE Type Y
(M to F)
IEN to DCE Type YA
(M to F)
V.35
IEN to DTE Type VX
(M to F) IEN to DCE Type V (M to M) Type VF (M to F) Type V (M to M) Type VF (M to F) Type V (M to M) Type VF (M to F) Type V (M to M) Type VF (M to F)
2 X DB25 DTE Type 2VE
(M to F) Type 2VE (M to F) Internal DSU 56/64Kbps Type DDS (M to M) T 1 C o n n ec t Netw o rk Di g ita l/ V o ic e DB15 PBX TELCO Network DB15 CSU/ DSU RJ45 PBX Token Ring STP UTP Ethe rn e t UTP BNC AUI Backplane Extension RJ11 Type RJ11(M to M) Type RJ11(M to M) 2 X RJ11
Table 7-2 Port processor cable requirements
Port processor
CID63 DSX11 DTC11 LHO DLA14
C o nne ct io n Int e rfa ce De vic e V.35 DTE + RS232 DTE Analog Voice 2 x RJ45 Type ALG-4W(M to F) 4 x RJ11 Type ALG-2W(M to F) Punch Down Type ALG-PD 2- or 4-wire Voice (M to P/D) Type ALG-PD-2W 2-wire Voice (M to P/D) Type ALG-PD-4W 4-wire Voice (M To P/D) RS232
IEN to DTE Type D1 (M to F) IEN to DCE Type A1
(M to M) RS232 X 3 IEN to DTE IEN to DCE V.35
IEN to DTE Type VX1 (M to F) IEN to DCE Type V1 (M to M) Type VF1 (M to F) 2 X DB25 DTE Type Y(63)(M to F) Internal DSU 56/64Kbps Type DDS 2 (M to M) T 1 C o n n e ct N e tw or k Dig ita l/V o ic e DB15 PBX Type T1-15-XF(F to M) TELCO Network Type T1-45-M(M to M) DB15 CSU/ DSU Type T1-K(M to M) RJ45 PBX Type T1-45-XF(M to F) Token Ring STP UTP Ethe rn e t UTP BNC AUI
ISDN-ST Type ISDN-ST(M to M) RJ11 Type RJ11(M to M) 2 X RJ11 Type T(63)(M to F)
Table 7-3 Port processor cable requirements
Port processor
LTR61 LTR61B LTR61H LET61 LET61B LET61H
Connect io n I n te rf ace Devi ce V.35 DTE + RS232 DTE Analog Voice 4 x RJ11 Punch Down RS232 DTE DCE RS232 X 3 DTE DCE V.35 DTE DCE 2 X DB25 DTE Internal DSU 56/64Kbps T1 Con n e ct N e tw or k Dig ita l/V o ic e DB15 PBX TELCO Network DB15 CSU/DSU RJ45 PBX Token Ring STP Type TR (M to AMP) Type TR (M to AMP) Type TR (M to AMP) UTP Type UTR-45M
(M to M) Type UTR-45M (M to M) Type UTR-45M (M to M) Et h e rn e t
UTP Type UET
(M to M) Type UET (M to M) Type UET (M to M) BNC Type LEC01 (BNC Adapter) Type LEC01 (BNC Adapter) Type LEC01 (BNC Adapter)
AUI Type LAU01
(AUI Adapter)
Type LAU01 (AUI Adapter)
Type LAU01 (AUI Adapter)
Backplane Expansion w/o Hub Type UET Cross
Note: With the network designed and the hardware and software specified, contact your Hypercom project manager to place your network order.
Table 7-4 IEN chassis cable requirements
Chassis
IEN 500 IEN 2000 IEN 2500 IEN 3000 IEN 4000 IEN 5000
C o nnec ti o n Int e rfa ce Dev ic e V.35 DTE + RS232 DTE Analog Voice 4 x RJ11 Punchdown RS232 DTE DCE RS232 X 3 DTE DCE V.35 DTE DCE 2 X DB25 DTE Internal DSU 56/64Kbps T 1 C o nnec t Ne two rk D ig ita l/ V o ic e DB15 PBX TELCO Network DB15 CSU/DSU RJ45 PBX Token Ring STP UTP Ethe rn e t UTP BNC AUI
Backplane Extension N/A Type HB2(M to M) Type HB2(M to M) Type B(AMP to AMP) Type HB3(M to M) Type B(AMP to AMP) 2 X RJ11
I n d e x
Numerics
56K/64Kbps DDS . . . .3-8
A
Adaptors . . . .7-2
Adaptors and cables. . . .7-2
Assigning node classifications . . . .2-3
Regional . . . .2-4
Remote . . . .2-4
Async port processor software matrix . . . .6-9
B
Backbone topologies Determining . . . .3-9 Frame Relay . . . .3-5 HDLC . . . .3-3 X.25 . . . .3-4Bisync port processor software matrix . . . .6-10
C
Cable and adaptors
General information . . . .7-3
Cable matrix
Port processors . . . .7-4
Cables . . . .7-2
Cables and adaptors . . . .7-2
Defining . . . .7-2 Determining . . . .7-2 Chassis . . . .5-2 IEN 100 . . . .5-2 IEN 2000 . . . .5-3 IEN 2500 . . . .5-3 IEN 4000 . . . .5-3 IEN 500 . . . .5-2 IEN 5000 . . . .5-4 IEN 6000 . . . .5-4 Chassis matrix IEN . . . .7-7 Classification
For central node . . . .2-3
For regional node. . . .2-3
For remote node . . . .2-3
Considerations
For network design . . . 2-2
Creating a network map . . . 4-2
D
Defining cables and adaptors . . . 7-2
Defining local port processor software requirements . 6-8
Defining local port processors and modules. . . 4-8
Defining network requirements. . . 2-1
Defining the WAN topology . . . 3-2
Defining WAN port processor software requirements .
6-2
Defining WAN port processors and modules . . . 4-3
Definitions Central node . . . 1-2 Logical node. . . 1-2 Node . . . 1-2 Node ID . . . 1-2 Port. . . 1-2 Port processor. . . 1-2 Regional node . . . 1-2 Remote node . . . 1-3 Slot . . . 1-3 Slot connector. . . 1-3
Slot connector number . . . 1-3
Slot number . . . 1-3
Determining cables and adaptors . . . 7-2
Determining node WAN requirements . . . 3-10
Determining the WAN topology . . . 3-9
Determining WAN port processors and modules . . 4-8
Dial backup . . . 4-4
Dial backup flowchart. . . 4-4
E
Ethernet port processor software matrix . . . 6-13
F
Flowcharts
Dial backup . . . 4-4
Frame Relay WAN . . . 4-5
HDLC local. . . 4-9
PBX/key system . . . 4-11
Voice over Frame Relay. . . 4-7
Fractional T1 . . . 3-8
Frame Relay . . . 3-5
Frame Relay WAN. . . 4-5
Frame Relay WAN flowchart . . . 4-5
G
Gathering network requirements. . . 2-2
General hardware information . . . 7-3
H
HDLC . . . 3-3 HDLC local . . . 4-9 HDLC local flowchart . . . 4-9 HDLC WAN. . . 4-6 HDLC WAN flowchart . . . 4-6HDLC/Frame Relay WAN port processor software 6-3
Hypercom terminology . . . 1-2 Central node. . . 1-2 Logical node . . . 1-2 Node. . . 1-2 Node ID . . . 1-2 Port . . . 1-2 Port processor . . . 1-2 Regional node. . . 1-2 Remote node. . . 1-3 Slot . . . 1-3 Slot connector . . . 1-3
Slot connector number . . . 1-3
Slot number . . . 1-3
I
Identifying network communication points . . . 3-10
IEN 100 . . . 5-2 IEN 2000 . . . 5-3 IEN 2500 . . . 5-3 IEN 4000 . . . 5-3 IEN 500 . . . 5-2 Ethernet . . . .6-13 SDLC . . . .6-17 Token Ring . . . .6-18
Local port processor software requirements
Defining . . . 6-8
Local port processors and modules
Defining . . . 4-8
M
Matrices
Async port processor software . . . 6-9
Bisync port processor software . . . 6-10
,
6-11Ethernet port processor software. . . .6-13
HDLC/Frame Relay WAN port processor software
. . . 6-3
IEN chassis cables . . . 7-7
ISDN port processor software . . . 6-5
Port processor cables . . . 7-4
SDLC port processor software. . . .6-17
Token Ring port processor software . . . .6-18
Voice port processor software. . . .6-21
X.25 port processor software . . . 6-7
N
Network communications points . . . .3-10
Network design considerations . . . 2-2
Network design process . . . 1-4
Network map Creating . . . 4-2 Network requirements Gathering . . . 2-2 Node classification . . . 2-3 Assigning . . . 2-3 Regional node . . . 2-4 Remote node . . . 2-4 Central . . . 2-3 Regional . . . 2-3 Remote . . . 2-3
Node WAN requirements
Determining . . . .3-10
PBX/Key system interface flowchart . . . .4-11
Physical interfaces
For WAN protocols . . . .3-8
Port processor software
Selecting . . . .6-1
Port processor software matrix
Async . . . .6-9
Bisync . . . 6-10
,
6-11Ethernet . . . .6-13
HDLC/Frame Relay WAN . . . .6-3
ISDN . . . .6-5 SDLC . . . .6-17 Token Ring . . . .6-18 Voice. . . .6-21 X.25 . . . .6-7 Port processors Selecting . . . .4-1
S
SDLC port processor software matrix . . . .6-17
Selecting chassis . . . .5-2
Selecting port processor software . . . .6-1
Selecting port processors . . . .4-1
Selecting WAN toplogy . . . .3-1
Software matrix
Async . . . .6-9
Asynchronous . . . .6-9
Asynchronous or serial IENView access. . . . .6-16
Bisync . . . 6-10
,
6-11 Bisynchronous. . . .6-10 Dial Backup . . . .6-5 Ethernet . . . .6-13 Frame Relay . . . .6-4 HDLC user services . . . .6-19 HDLC WAN . . . .6-3HDLC/Frame Relay WAN . . . .6-3
ISDN . . . .6-5 SDLC . . . .6-17 T1/E1 interface . . . .6-6 Token Ring . . . .6-18 Voice. . . .6-21 X.25 . . . .6-7
T
T1 . . . .3-8 Terminology . . . .1-2Token Ring port processor software matrix . . . .6-18
V
Voice over Frame Relay . . . .4-7
Voice over Frame Relay flowchart. . . 4-7
Voice port processor software matrix . . . 6-21
W
WAN physical interfaces
56K/64Kbps DDS . . . 3-8
T1 or Fractional T1 . . . 3-8
WAN port processor software
HDLC/Frame Relay . . . 6-3
ISDN. . . 6-5
Voice . . . 6-21
X.25 . . . 6-7
WAN port processor software requirements
Defining . . . 6-2
WAN port processors and modules
Defining . . . 4-3 Determining . . . 4-8 WAN protocols Frame Relay . . . 3-5 HDLC . . . 3-3 Physical interfaces . . . 3-8 X.25 . . . 3-4 WAN topology Defining . . . 3-2
X
X.25 . . . 3-4Reader Comment Form
Please forward any comments about this document to:Hypercom Corporation
Technical Information Development 2851 West Kathleen Road
Phoenix, Arizona 85023 http://www.hypercom.com
