Specifications

ManualsBrandsBlack Box ManualsComputer equipment5000 MX215C, 5000 MX218C

Order toll-free in the U.S. 24 hours, 7 A.M. Monday to midnight Friday: 877-877-BBOX

FREE technical support, 24 hours a day, 7 days a week: Call 724-746-5500 or fax 724-746-0746

Mail order: Black Box Corporation, 1000 Park Drive, Lawrence, PA 15055-1018

Web site: www.blackbox.com • E-mail: info@blackbox.com

CUSTOMER

SUPPORT

INFORMATION

OCTOBER 1994

MX219A

MX215C, MX218C

MX222C, MX223C

MX224, MX226C

MX228C, RM220

Multiserver 5000

MULTISERVER 5000

EXE

Summary of content (268 pages)

PAGE 1
OCTOBER 1994 MX219A MX215C, MX218C MX222C, MX223C MX224, MX226C MX228C, RM220 Multiserver 5000 EXE VER ISER MULT CUSTOMER SUPPORT INFORMATION 5000 Order toll-free in the U.S. 24 hours, 7 A.M. Monday to midnight Friday: 877-877-BBOX FREE technical support, 24 hours a day, 7 days a week: Call 724-746-5500 or fax 724-746-0746 Mail order: Black Box Corporation, 1000 Park Drive, Lawrence, PA 15055-1018 Web site: www.blackbox.com • E-mail: info@blackbox.
PAGE 2
Multiserver 5000 Multiserver 5000 Multiserver 5000 CommPak MS5 Expansion Module Sync/Async MS1 Expansion Module—Async only MS1 Expansion Module—12 Async—RJ-45 MS1 Expansion Module—12 Async—RJ-45 w/Line Drivers MS1 V.35 Converter/DCE MS1 X.21 (V.11) Converter MS1 Rackmount Kit Installation and Operation Manual Warning Access to the interior of the unit for such purposes as replacing fuses, or any other maintenance-type of procedure, must be performed only by a qualified technician.
PAGE 3
Multiserver 5000 FEDERAL COMMUNICATIONS COMMISSION RADIO FREQUENCY INTERFERENCE STATEMENT This equipment generates, uses, and can radiate radio frequency energy and if not installed an used properly, that is, in strict accordance with the manufacturer's instructions, may cause interference to radio communication.
PAGE 4
Table of Contents Table of Contents 1. Specifications Multiserver 5000 (Base Unit) ..................................................................................................13 Expansion Modules..................................................................................................................15 MS1 Voice/Fax Cards ..............................................................................................................16 MS1 56K CSU/DSU Module .....................................
PAGE 5
Multiserver 5000 Table of Contents (continued) 3.5 Default Node Numbers and Node IDs ............................................................................27 3.6 Examples of Network Designs ..........................................................................................29 Single Link Point-to-Point.........................................................................................................29 Dual Link Point-to-Point ................................................................
PAGE 6
Table of Contents Table of Contents (continued) 5.5.7 Removing the CCM .........................................................................................................46 5.6 Installation Procedures.....................................................................................................47 5.6.1 Install the Spacers ...........................................................................................................47 5.6.2 Install the CCM............................................
PAGE 7
Multiserver 5000 Table of Contents (continued) External CSU/DSU to Internal CSU/DSU .............................................................................62 External CSU/DSU to External CSU/DSU.............................................................................62 CCM Indicators .........................................................................................................................62 Final Installation...........................................................................
PAGE 8
Table of Contents Table of Contents (continued) Introduction to X.21 .................................................................................................................77 Port Configuration for the X.21 Link ......................................................................................77 Configuration of X.21 Link Parameters ..................................................................................77 Install the X.21 Link.........................................................
PAGE 9
Multiserver 5000 Table of Contents (continued) Fixed Destination Connection ...............................................................................................112 Class Connections ...................................................................................................................112 Node/Class Connection .........................................................................................................113 Matrix Connection ...................................................
PAGE 10
Table of Contents Table of Contents (continued) Dialog Messages.......................................................................................................................141 11.5 Network Security ...........................................................................................................144 Passwords .................................................................................................................................141 Lock-Out Configuration ..........................
PAGE 11
Multiserver 5000 Table of Contents (continued) 13. LCD/Keypad 13.1 General LCD/Keypad Information .............................................................................165 LCD Blinking Backlight ..........................................................................................................166 Keypad Reset............................................................................................................................166 LCD/Keypad Password Protection..............................
PAGE 12
Table of Contents Table of Contents (continued) Display Messages Worksheet..................................................................................................188 Voice/Fax Parameters Worksheet.........................................................................................189 Record of Passwords ..............................................................................................................190 Appendix B: Cabling Diagrams Cabling for the CCM and 6-Channel CEMs ..........
PAGE 13
Multiserver 5000 Table of Contents (continued) Fast Packet ...............................................................................................................................217 Voice/Fax Module .................................................................................................................218 KTS Interface...........................................................................................................................218 E&M Interface .................................
PAGE 14
CHAPTER 1: Specifications 1. Specifications Multiserver 5000 (Base Unit) Physical Specifications MX219A Performance Specifications Expansion — up to 4 modules (in locations B, C, D, and E) and the NMS module (underneath the CCM).
PAGE 15
Multiserver 5000 Multiserver 5000 (continued) Async Channel Characteristics Sync Channel Characteristics Capacity — up to 41 Capacity — up to 10 Speed — 50 to 38,400 bps Speed — External clocking: Internal clocking: DLC: ASCII Bisync: H-P Sync: RTS/CTS: Sync-Pad: EBCDIC Bisync: Micom DLC Micom Voice: Fast Packet: TDM: Configuration — DCE ABR — to 19.2 Kbps Parity — Odd, Even, Mark, Space, None Stop Bits — 1, 1.
PAGE 16
CHAPTER 1: Specifications Expansion Modules MS1 Expansion Module—12 Async—RJ-45 MX223C MS5 Expansion Module Sync/Async MX215C Connectors — (6) DB25 (female) Interface — RS-232, V.24/V.28 Transmission Mode — Serial async; full-duplex Connectors — (12) RJ-45 (female) Interface — RS-232, V.24/V.
PAGE 17
Multiserver 5000 MS1 Voice/Fax Cards MX225C-1 AND MX225C-2 General Specifications Analog Specifications Channels per Voice/Fax Card — MX225C-1: One channel MX225C-2: Two channels Insertion Loss — 2 dB nominal @ 1000 Hz (End-toEnd) Signals Supported — Analog voice and Group III fascimile (fax) Telephone Interfaces — PBX tie trunk: E&M Types I through V, 2-wire or 4-wire; PBX station or Central Office PSTN: OPX Loop Start, 2-wire; Key telephone systems, telephone set or PBX CO Trunk: KTS Loop Start, 2-wi
PAGE 18
CHAPTER 1: Specifications MS1 Voice/Fax Cards (continued) MX225C-1 AND MX225C-2 Signaling Specifications Digital Specifications Formats — Channel Digitizing Rates — 4.8, 6.4, 7.2, 8, 9.6, 12, 14, and 16 Kbps Dial Pulse: ≤3% distortion @ 10 pulses per second Dual Tone Multifreq: ≤1% distortion Steady DC (E&M): Types I, II, III, IV, and V Single Frequency: 2280 Hz (AC15) on E&M 4 wire interface only Pulsed DC (RonTron): E&M interface only Fascimile Rates — Group III fax at 9.6, 7.2, 4.8, and 2.
PAGE 19
Multiserver 5000 MS1 56K CSU/DSU Module MS RLB Module MT150C MX229A Network Application — 4-wire DDS interface to AT&T Digital Data Service network (or equivalent) Connectors — 15-pin AUI connector or BNC connector Data Rate — 56 Kbps Connectors — RJ-48S (USOC) 8-pin modular jack Transmission Mode — Synchronous; full-duplex Loop Range — 15,000 feet (4572 m) over 26 AWG wire Output Signal — Pulse amplitude 1.4 to 2.
PAGE 20
CHAPTER 1: Specifications MS1 NMS Module MS1 V.35 Converter/DCE MX227C MX226 Command and Printer Ports: Converter — RS-232 to V.35 Connector — DB25 (female) Interface — RS-232/V.24/V.28 Transmission Mode — Serial async Data Rates — Up to 19.2 Kbps Connectors — To Central Control Module: DB25 (male) To V.35 Connector: DB25 (female) Cable (included) — 5-foot DB25 (male) to 34-pin M-block (male) Alarm Relay Connector — 4-position terminal block X.21 Converter/DCE MX228C Converter — RS-232 to X.
PAGE 21
Multiserver 5000 2. Introduction 2.1 The Multiserver 5000 (Base Unit) separate pieces of equipment to transmit these four different types of signals. The Multiserver 5000 is a communications-network multiplexor.
PAGE 22
CHAPTER 2: Introduction 2.2 Feeder Muxes three (3) high-speed interconnect links (a Multiserver-to-Multiserver connection) in ports A1 to A3, five (5) mux links (a Multiserver-to-feedermux connection) in ports A1 to A5, or five (5) data input/output channels in ports A2 to A6. The Multiserver 5000 can support up to five (5) feeder muxes. Each feeder mux can support both async data channels and voice/fax channels.
PAGE 23
Multiserver 5000 The Multiserver line of products, including compatible and supporting products PRODUCT NAME ............................................................ORDER CODE PRODUCT NAME ............................................................ORDER CODE Multiserver 5000.....................................................................................MX219A MS1 56K CSU/DSU Module (cabling included) ................................MT150C Straight-Thru Male-to-Male Cable (for DTE) ............
PAGE 24
CHAPTER 2: Introduction 2.3 The CommPak The Multiserver 5000 Commpak plug-in software cartridge contains all of the Multiserver 5000’s operating software. To add features and program upgrades is simple—just change the cartridge. NOTE: The Multiserver 5000 CommPak cartridge is required for the unit to operate. 2.4 Expansion Modules Plug in up to three of these data expansion modules to suit your data networking needs; use any combination.
PAGE 25
Multiserver 5000 2.8 MS1 NMS Module (MX227C) The MS1 NMS Module (network management system module) fits underneath the CCM on the rear panel of the Multiserver 5000. It features a command port to hook up a PC or terminal, a printer log port to connect a serial printer, and an alarm relay. You can run diagnostic tests and generate statistics reports, and then print the results (logs) on your own connected printer. 2.9 MS1 V.35 Converter/DCE (MX226) The MS1 V.
PAGE 26
CHAPTER 2: Introduction 2.12 Manual Text Conventions This manual uses the following standard conventions: Partial menus are shown, and they will be in the following format: or cr Press the RETURN key on your keyboard Press the BREAK key on your keyboard Press the ESCAPE key on your keyboard ^ CONTROL key on the keyboard. Indicates that the Control key is to be held down while you press the key that follows this symbol.
PAGE 27
Multiserver 5000 26
PAGE 28
Multiserver 5000 3. Network Design and Topologies 3.1 Initial Considerations The Multiserver 5000 offers the ability to connect one of the following units and their associated links: • Multiserver (1000 or 5000) via an Interconnect Link. • Feeder Mux (Communication Box II or Statplex Multiplexor) via a Mux Link or an X.21 Link The interconnect link can be connected using the integral MS1 56K CSU/DSU module. Any of the links can be connected using an external ISU or modem.
PAGE 29
CHAPTER 3: Network Design and Topologies 3.2 Worksheets for the Network 3.4 Syntax for Node Numbers and IDs Appendix A contains worksheets you can use to plan your network. Make photocopies of the worksheets you will need and then complete them. You will need to refer back to your worksheets for other aspects of the configuration process later in this manual. Multiserver units and compatible multiplexors share the same syntax for the node numbers and IDs. 3.
PAGE 30
Multiserver 5000 Local Hub Group Remote Hub Group PORT CommBox II CommBox II A3 A4 A5 A1 A1 A2 A2 Multiserver 5000 A3 A4 A5 Multiserver 5000 CommBox II CommBox II CommBox II CommBox II Figure 3-1. In this distributed star, A1 and A2 are interconnect links. A3, A4, and A5 are mux links. A1 Multiserver 5000 A2 Multiserver 5000 Multiserver 5000 Figure 3-2. A1 and A2 are interconnect links. A1 CommBox II A2 Multiserver 5000 CommBox II Figure 3-3. A1 and A2 are mux links.
PAGE 31
CHAPTER 3: Network Design and Topologies 3.6 Examples of Network Designs SINGLE LINK POINT-TO-POINT The most basic of topologies is the point-to-point: point A to point B. A point-to-point switching topology is shown in Figure 3-4. Multiserver 5000 units can operate in a point-to-point switching topology over terrestrial, satellite, and microwave services at speeds ranging from 9.6 to 72 Kbps. Feeder muxes can be attached to either or both ends of the network.
PAGE 32
Multiserver 5000 DUAL LINK POINT-TO-POINT Figure 3-5 illustrates a dual-link, point-to-point application. All traffic between Multiserver nodes is loadbalanced between Link A and Link B. In the event of a single link failure, all traffic is automatically rerouted over the secondary link (link B). In a single-link, point-to-point application, the interconnect link can be configured from 9.6 to 72 Kbps. When load-balancing, each link must necessarily be slower that in a single-link application.
PAGE 33
CHAPTER 3: Network Design and Topologies STRING If several Multiserver units are strung together, a string topology is created (Figure 3-6). The limitations to this application are the following: • Maximum six hops • No closed loops Any or all of these may be Multiserver 5000 units. Three Multiserver units in a string can also be considered a “V” or drop-and-insert application (see Figures 3-7 and 3-8).
PAGE 34
Multiserver 5000 STAR The star topology (Figure 3-9) is a network with a single major center (hub) connected to (up to) five access points. The Multiserver 5000 can have three of the links connected to other Multiserver units with two additional links connected to feeder muxes. HOST MULTISERVER 5000 MULTISERVER 1000 MULTISERVER 5000 NETman Command Terminal FAX PBX Figure 3-9. Typical Star Application.
PAGE 35
CHAPTER 3: Network Design and Topologies DISTRIBUTED STAR If two Multiserver star networks are connected, the topology can be described as a distributed star. Figure 3-10 shows two star networks connected to form a distributed star. FEEDER MUX MULTISERVER 1000 FEEDER MUX MULTISERVER 5000 MULTISERVER 1000 MULTISERVER 1000 MULTISERVER 1000 FEEDER MUX FEEDER MUX Figure 3-10. Typical Distributed-Star Application.
PAGE 36
Multiserver 5000 4. Base-Unit Installation This chapter explains how to install the Multiserver base unit. Once installation is completed, you will be ready to configure. It is assumed that your Multiserver has all optional modules already installed. Module installation is discussed in chapter 5. You should not hook up the interconnect link or the system can generate an error message. Distance to AC Power Socket: Should not exceed six feet (1.8 meters).
PAGE 37
CHAPTER 4: Base-Unit Installation 4.2 CommPak Cartridge Installation and Removal INSTALLING THE COMMPAK CARTRIDGE The CommPak cartridge contains the operating software for the Multiserver. When a cartridge is not being used, it should be stored in an anti-static bag. It is assumed that the CCM is installed. You cannot install the CommPak cartridge unless the CCM is installed.
PAGE 38
Multiserver 5000 On the front of the unit is a liquid-crystal display (LCD). After the unit completes its internal tests, the clock will start and the LCD will display a message. The LCD backlight will also flash. This indicates that there is alarm message, probably Local Link Multiserver 5000 Time: 00:01:23 LCD DISPLAY reset A1. This means that the default link channel has been reset. The backlight will eventually time out. See Section 13.
PAGE 39
CHAPTER 4: Base-Unit Installation Table 4-1.
PAGE 40
Multiserver 5000 the Multiserver 5000. • The CCM module has six connectors and is located in module location A. From left to right these connectors are numbered sequentially (1 to 6). The channel numbers correspond to the module and connector locations. The channel number for the connector on the far left side is A1. The next connector to the right is A2, and so on to the last connector, A6. • The NMS Module has two channel numbers: The Log Port is $1 and the Command Port is $2.
PAGE 41
CHAPTER 4: Base-Unit Installation J16 J13 J11 J14 PORT 6 BATTERY J15 PORT 5 E1 Jumper E1 PORT 4 PORT 3 PORT 2 J17 J18 PORT 1 J1 J2 J3 J4 Figure 4-9. The CCM Board. The front-panel of the unit is to the left.
PAGE 42
Multiserver 5000 5. Module Installation 5.1 Module Stacking Order • 6-channel CEM Although you are not actually installing the modules yet, it is important to become familiar with the five chassis positions available for modules in the Multiserver unit. These are identified from bottom to top as module locations A through E (see Figure 5-1). The possible hardware-configuration combinations are numerous.
PAGE 43
CHAPTER 5: Module Installation SWITCH GROUP S1 1 2 3 4 N OPE FOR MODULE LOCATION B Figure 5-2. N OPE FOR MODULE LOCATION C N OPE FOR MODULE LOCATION D N OPE FOR MODULE LOCATION E Switch S1 and module location settings. Up position = open = off Down position = closed = on 5.2 Module-Location Switch Settings Each expansion module has a module-location switch group S1 that informs the software of its location in the Multiserver unit (see Figure 5-2).
PAGE 44
Multiserver 5000 5.3 Inter-Module Stacking Connectors The modules are powered via the stacking connector located on the front right side looking from the front of the Multiserver unit. In Figure 5-3, the back of the unit is shown, and the connectors are therefore on the left. A stacking connector has two parts: a shroud and a block. The shroud is on the bottom of the module being installed and fits over the block on the module below. As you position the module, align the shroud and the block.
PAGE 45
CHAPTER 5: Module Installation BLANK PANEL Figure 5-4. The back of a multiserver unit with a blank panel. 5.4 Blank Back Panel 5.5 Disassembly Procedures The unit is delivered with blank back panels to eliminate an open area in the rear of the unit where there are no modules installed (Figure 5-4). Do not discard unused blank back panels; they may be needed later.
PAGE 46
Multiserver 5000 A2 A1 A4 A3 A6 A5 AT BO Figure 5-6. Remove the cover after taking out four fastening screws. 5.5.1 UNPLUG THE MULTISERVER Remove the power cord from the wall outlet. The Multiserver unit contains electrosensitive components that could suffer damage from static discharge. Ground yourself by touching any grounded equipment. Touching the Multiserver’s chassis will not work. Since the unit is now unplugged, it is no longer grounded. 5.5.
PAGE 47
CHAPTER 5: Module Installation Figure 5-8. Remove any blank panels. cover. The delicate metallic finger stocks are located at the front and rear of the cover. They are needed to make contact with the bottom enclosure and to ensure compliance with FCC Part 15 or FTZ radiated emission standards. 5.5.3 REMOVE BLANK BACK PANELS Each blank back panel is supported by two retaining screws. To remove the panel, unscrew and remove the screws. Then pull off the panel.
PAGE 48
Multiserver 5000 5.5.4 REMOVE SPACERS Inside the front of the Multiserver unit, there are six spacers for positioning the modules (see Figure 5-9). To remove a spacer, simply slide the spacer up and out of the unit. Set the spacers aside for reassembly. The bottom-most spacer (the number 1 spacer in Figure 5-9) should remain in the unit. including the CCM. Follow the CCM Removal instructions (Section 5.5.7). Refer to the MS1 NMS Module User’s Manual for installation guidelines. 5.5.
PAGE 49
CHAPTER 5: Module Installation 5. Disconnect the fan connector from the CCM. 6. Disconnect the 34-pin NMS module ribbon cable, if it is installed. 7. Unscrew the two screws in the back panel. 8. Gently remove the board by lifting it up. 5.6 Installation Procedures The Multiserver unit contains electrosensitive components that could suffer damage from static discharge. Ground yourself by touching any grounded equipment. You cannot ground yourself by touching the Multiserver’s chassis.
PAGE 50
Multiserver 5000 5. Connect the 26-pin LCD ribbon cable to the CCM. 6. Connect the fan connector to the CCM. 7. Connect the 34-pin NMS Module ribbon cable, if installed, to the CCM. 8. Place a spacer on top of the CCM by inserting it at the top of the bezel at the front of the unit and then sliding it down until it rests on the module . 2. Set switch group S1 according to the module location switch setting (see Section 5.2, Module Location Switch Settings). 3.
PAGE 51
CHAPTER 5: Module Installation • Figure 5-13. Reinstalling spacers. 5.6.4 REMAINING SPACERS When finished installing the modules, reinstall any remaining spacers. 5.6.5 INSTALLING BLANK BACK PANELS The space above the last module installed must be filled with blank back panels for the following reasons: • To provide a safe unit • To ensure proper air flow over the modules To be in compliance with radiated emission standards such as FCC Part 15 and FTZ. To install, first locate the top side of the panel.
PAGE 52
Multiserver 5000 5.6.6 PUT THE COVER BACK ON 1. Be sure that all spacer positions have been filled before replacing the cover to ensure proper module connections. 2. Be sure blank back panels have been installed into the back of the unit to eliminate open spaces. 3. Be careful not to handle the delicate metallic finger stocks when installing the cover.
PAGE 53
CHAPTER 5: Module Installation 5.7 Converters (Optional Equipment) 1. Attach the converter to the desired port by matching the DB25 connector. The converter is attached externally to the Multiserver unit. The V.35 and X.21 Converters consist of an adapter (which connects directly to the Mulitserver) and a cable. The cable is included with the V.35 converter. The cable is not included with the X.21 converter. See Appendix B for cabling diagrams. 2.
PAGE 54
Multiserver 5000 6. Getting Started 6.1 Multiserver Base Unit Location Your Multiserver should be installed at its location. If you have a Rackmount Kit, install it now (see Appendix G). Place the Multiserver in the Rackmount Tray when completed. 6.2 Connecting an ASCII Terminal You will need to connect an ASCII terminal to the Multiserver in order to access the Command Mode and the Command Facility. The Command Mode offers complete configuration and administration options.
PAGE 55
CHAPTER 6: Getting Started 6.3 The Command Facility The Command Facility contains menus to configure the ports, node, and data channels. You will need to access the Command Facility often during the configuration process. When an ASCII terminal is connected, the screen is blank except for the cursor position. From here you can enter the Command Facility in one of two ways: • Via the Command Mode using ^X . The advantage of ..
PAGE 56
Multiserver 5000 ACCESS THE COMMAND FACILITY VIA $CMD Press . At the ENTER CLASS prompt, enter $CMD. ENTER CLASS: EXITING THE COMMAND FACILITY To Exit the Command Facility, press or select option 12. EXIT COMMAND FACILITY. $CMD 12 EXIT COMMAND FACILITY There is no default password. Just press . The DISCONNECT message is displayed. ENTER CLASS PASSWORD: The Command Facility Main Menu appears. COMMAND FACILITY MAIN MENU [node id] 1. VIEW CONFIGURATION 2. STATUS/STATISTICS 3.
PAGE 57
CHAPTER 6: Getting Started 6.4 Reset Defaults • Perform a cold start using the front-panel keypad. Refer to Figure 6-2. Use one of the following methods to ensure that the Multiserver’s configurations are set to standard default values. • Enter the Command Facility Main Menu to perform a cold start.
PAGE 58
Multiserver 5000 6.5 Name the Local Node You will need to assign the local node a number and name to differentiate it from remote nodes. Refer to the worksheets you used in connection with Chapter 3.0, Planning Your Network. Before proceeding, please review: Section 3.3 Nodes and Hubs Section 3.4 Syntax for Node Numbers and IDs Section 3.
PAGE 59
CHAPTER 6: Getting Started When you have entered a valid number and ID, the following message will appear: **SELECT “Y” TO RESET SYSTEM WHEN NODE CHANGES MADE** ENTER “Y” TO RESET OR “C” TO CONTINUE: Y LCD/KEYPAD CONFIGURATION You can name the local node on the front-panel keypad. See the Local Node Number and ID discussion in Section 13.5 Administration for instructions on this procedure. NMS SWITCH CONFIGURATION The S1 switch bank on the NMS Module can be used to configure the local node’s name and ID.
PAGE 60
Multiserver 5000 6.6 Quick Setup CAN YOU DO A QUICK SETUP? A quick installation can be done to get a point-topoint Multiserver network up and running in a short amount of time. You will be force-connecting all the channels within the network (A2 to A2, A3 to A3, etc.). Only channels of like type will be connected. Voice channels cannot be forceconnected to data channels, so all hardware components must match. Caution PRELIMINARY STEPS • All modules should be installed in the base unit (see Chapter 5.
PAGE 61
CHAPTER 6: Getting Started THE FORCE-CONNECTION The force-connection is accessed through the Command Facility. Press . After all channels have been force-connected, you can connect terminals to the ports and pass data between them. Individual channels can be reconfigured as the need arises. ENTER CLASS: $CMD ENTER CLASS PASSWORD: For more information on force connections, see Chapter 10.0, Switching Configuration and, in particular, Section 10.2, Point-to-Point Dedicated (Force Connect All).
PAGE 62
Multiserver 5000 7. Bench Configuration and Testing Important 7.1 Overview You should configure a node number and ID for each of your Multiservers and substitute those names in the directions as appropriate. This chapter discusses setting up your Multiserver network before it is installed in remote locations. Configuring and testing your network in one location before its final installation will alleviate many problems that would result from not having a Network Manager at each of your remote sites.
PAGE 63
CHAPTER 7: Bench Configuration and Testing MS1 56K CSU/DSU Module E VOICE CHANNEL 1 KTS OPX VOICE CHANNEL 1 KTS OPX VOICE CHANNEL 2 SB M E SG R1 T1 R T SB M E SG R1 T1 R T KTS OPX KTS OPX VOICE CHANNEL 2 SB M E SG R1 T1 R T SB M E SG R1 T1 R T D Local Multiserver 5000 C B 1 CCM 2 1 3 2 4 5 3 6 7 8 4 9 10 11 5 12 6 A A B C EZ423 EZ423 EL08M EL08M EL08M CSU/DSU MS (MT132A-R2) EZ423 E D VOICE CHANNEL 1 KTS OPX VOICE CHANNEL 2 SB M E SG R1 T1 R T CCM KTS OPX SB M
PAGE 64
Multiserver 5000 7.2 Using CSU/DSUs with the Interconnect Link Figure 7-2 illustrates a Multiserver network, with a Multiserver 5000 as the central hub and three other Multiservers attached to the local hub. Each interconnect link is set up differently. The CSU/DSU MS (MT132A-R2) is used in these examples as the external CSU/DSU. This CSU/DSU can be configured for RS-232 operation, saving you the expense of the V.35 Converter (MX226).
PAGE 65
CHAPTER 7: Bench Configuration and Testing Local Multiserver Remote Multiserver E E D D C C B 1 2 3 4 5 6 B 1 2 A EZ423 3 4 5 6 A EZ423 Crossover Cable Modem Modem Figure 7-3. Modems can be used to connect two Multiservers via an interconnect link. 7.3 Using Modems with the Interconnect Link Figure 7-3 illustrates how modems can be used to connect two Multiservers. The modems you use with your Multiservers must be V.
PAGE 66
Multiserver 5000 7.4 The Sync Data Channel Because of the myriad of different protocol and equipment combinations available for sync data channels, there is no simple test that will ensure your sync application will run smoothly. You will need to complete data-channel configuration and then test your specific application. The equipment at your local site must be able to emulate the equipment at your remote site for you to be able to include sync data channels in your Bench Configuration process.
PAGE 67
CHAPTER 7: Bench Configuration and Testing Port A4 Port A5 E D C B 1 2 3 4 5 Local Multiserver 6 A Straight-Through Male-to-Male Cable (EZ422) or Straight-Through Male-to-Female Cable (EDN16C-M/F) Interconnect link Async terminal Async terminal (DTE, DB25) (DTE, DB25) Port A6 E D C Remote Multiserver B 1 2 3 4 5 6 A Straight-Through Male-to-Male Cable (EZ422) or Straight-Through Male-to-Female Cable (EDN16C-M/F) Async terminal (DTE, DB25) Figure 7-5.
PAGE 68
Multiserver 5000 7.5 Testing Asynchronous Data Channels During the Bench Configuration, you can test async data channels on the CCM and any Channel Expansion Modules that are installed in your Multiserver. ASYNC CHANNELS ON THE LOCAL NODE To connect and test a pair of async data ports, proceed as follows: 1. Configure two async terminals per Table 7-1. Table 7-1.
PAGE 69
CHAPTER 7: Bench Configuration and Testing RLB Module FC115 FC135 E ThinNet Coax Cable (LCN300) D C MS RLB COMMPAK B Transceiver 1 2 3 4 5 6 A Local Multiserver Interconnect Link File server Remote Multiserver E D C MS RLB COMMPAK B 1 2 3 4 5 6 A FC135 PC with Ethernet card Ethernet card FC115 RLB Module PC ThinNet Coax Cable (LCN300) Figure 7-6. Testing the RLB Module in a ThinNet environment. (See next page for explanation.
PAGE 70
Multiserver 5000 7.6 Testing the RLB Module During Bench Configuration, you can quickly test your MS RLB Modules to verify that they are working properly. THINNET By default, the BNC connector on the RLB Module is active. ThinNet Ethernet can connect directly to the back of the RLB Module. No external transceiver is necessary. The first step is to connect the Local Multiserver to the local Ethernet LAN. See Figure 7-5. • Attach a BNC Coaxial T Connector (FC115) to the BNC connector on the RLB Module.
PAGE 71
CHAPTER 7: Bench Configuration and Testing Cable (included with Voice/Fax module) Cable (included with Voice/Fax module) Phone E E D D C KTS OPX VOICE CHANNEL 1 VOICE CHANNEL 2 SB M E SG R1 T1 R T 1 KTS OPX SB M E SG R1 T1 R T 2 3 4 5 Phone C VOICE CHANNEL 1 B KTS OPX VOICE CHANNEL 2 SB M E SG R1 T1 R T 6 1 KTS OPX SB M E SG R1 T1 R T 2 3 4 5 B 6 A A Local Multiserver Remote Multiserver Interconnect Link Figure 7-7.
PAGE 72
Multiserver 5000 8. Link Configuration 8.1 Types of Links There are three types of links in the Multiserver system: An Interconnect Link connects two Multiservers (usually over an analog or digital circuit provided by the telephone company). A Mux Link connects a Multiserver to a compatible multiplexer. The Feeder Mux can be connected directly to the Multiserver or remotely using a line driver, modem, or ISU. An X.21 Link connects a Multiserver to a compatible multiplexer via an X.21 bis network. 8.
PAGE 73
CHAPTER 8: Link Configuration 8.4 Port Configuration Enter the node ID/port number. Example: NEWYORK/A2. Before the link is installed, the port assigned to the link must be configured. Configure the port after the local node is named (see Section 6.6, Name the Local Node). The Port Configuration Menu is accessed from the Configure Local Nodes Menu. The Port Configuration Menu then appears: PORT CONFIGURATION [xxx] 1. ASYNC 2. SYNC 3. INTERCONNECT LINK COMMAND FACILITY MAIN MENU [node id] 4.
PAGE 74
Multiserver 5000 8.5 The Interconnect Link PORT CONFIGURATION FOR THE INTERCONNECT LINK The Interconnect Link is for connection to another Multiserver. From the Port Configuration Menu, select option 3. For most applications, select Sync External Clocks. This is used when connecting to another Multiserver across a link via a communications device (CSU/DSU module, external CSU/DSU, or external modem).
PAGE 75
CHAPTER 8: Link Configuration When the local Multiserver 5000 connects to another Multiserver, it scans the remote Multiserver, reads the node ID and numbers of the remote Multiserver and feeder muxes, and stores the information in memory. CONNECTING MULTISERVER UNITS BACK TO BACK Follow these steps to connect a Multiserver directly to another Multiserver: 1. Configure a node name and number (other than the default) for each unit. 2. Configure a port on each unit for an interconnect link.
PAGE 76
Multiserver 5000 Next, select option 3 from the remote Command Facility menu. At the ENTER NODE-ID # [240] prompt, enter the node number. Press (refer to Section 3.4, Syntax for Node Numbers and IDs, to review syntax requirements). COMMAND FACILITY MAIN MENU [!240] 3 CONFIGURE LOCAL NODES It may seem to be a paradox to use the term “local node” when configuring the remote Multiserver.
PAGE 77
CHAPTER 8: Link Configuration 8.6 The Mux Link SET LINK RATE [SYNC EXTERNAL CLOCKS]: PORT CONFIGURATION FOR THE MUX LINK The mux link is for connecting the Multiserver to a feeder mux. The mux link can either be a leased line or a crossover cable to a locally-placed feeder mux. From the Port Configuration Menu, select option 4. PORT CONFIGURATION [xxx] 4 MUX LINK The next menu will appear: Most applications require option 1, Sync External SET LINK RATE [SYNC EXTERNAL CLOCKS]: 1. Sync External Clocks 2.
PAGE 78
Multiserver 5000 FEEDER MUX NODE IDS You should renumber and rename a feeder mux after configuring its link. Mux and X.21 links have default numbers and names according to the port they are assigned (see Section 3.5). If there is a problem ascertaining the mux node ID, you may display the node status. This will show the node names for local feeder muxes. See Section 8.8, Review Link Configuration. Local feeder muxes are those connected to the local Multiserver.
PAGE 79
CHAPTER 8: Link Configuration 8.7 The X.21 Link INTRODUCTION TO X.21 Unlike the mux links (leased-line links), which are permanently connected, X.21 is a pay-as-you-go link. When a signal is raised, the network automatically establishes the link to the remote side. When you are finished, the link is dropped until it is again needed. The link is established on demand. X.21 is for data-only channels; it does not support voice or fax channels. In X.
PAGE 80
Multiserver 5000 X.21 LINK PARAMETERS 1. LOCAL X.21 CONNECT MODE [DATA ACTIVITY CONNECT] 2. LOCAL X.21 NUMBER OF RETRIES 3. MB2 X.21 CONNECT MODE [20] [DATA ACTIVITY CONNECT] 4. MB2 X.21 NUMBER OF RETRIES [20] CR - ACCEPT DATA M - MAIN MENU ENTRY: Table 8-2. X.21 Link Parameters Option 1. Local X.21 Connect Mode Default Description Data Activity Connect Data Activity is currently the only option on this menu. Therefore, Data Activity Connect is the only option for Multiserver ports.
PAGE 81
CHAPTER 8: Link Configuration Table 8-2. X.21 Link Parameters (continued) Option 2. Local X.21 Number of Retries Default Description 20 This option selects the number of times the Multiserver will attempt to place a call over the X.21 network. The range is from 1 to 63 tries; the default is 20. When you select this option, the following prompt appears on the screen: ENTER LOCAL X.21 NUMBER OF RETRIES: [20] Enter the desired number. Press . To exit without changes, enter the same number as before.
PAGE 82
Multiserver 5000 X.21 CALLS INSTALL THE X.21 LINK Assuming that you have installed and configured the modem for the X.21 link, connect the cable. In X.21 link operation, the Multiserver must be connected to a feeder mux via an external modem. It cannot be connected to another Multiserver. An X.21 call is automatically initiated when: X.21 Link Configuration 1. Data Activity Data activity is detected (and buffered in the calling unit until synchronization is established with the remote unit). 2.
PAGE 83
CHAPTER 8: Link Configuration 8.8 Review Link Configuration The node ID and number appear at the top of the screen. To review node configuration, select option 2, Status/Statistics, from the Command Facility Main Menu. COMMAND FACILITY MAIN MENU [node id] 2 Each port configured as a link will be listed. The node ID and number of any attached Multiserver or feeder mux will be listed next to that port.
PAGE 84
Multiserver 5000 9. Data-Channel Configuration To configure data channels, the local node must be named. If you have not already named the local node, refer to Section 6.6, Naming the Local Node. CONFIGURE LOCAL NODES [node id] Data channels on remote Multiservers can be configured once the remote Command Facility is accessed. Local or remote feeder mux channels can also be configured from the Multiserver.
PAGE 85
CHAPTER 9: Data-Channel Configuration 9.2 Synchronous Channels Sync is supported only when directly attached to a Multiserver. Feeder muxes can only support async or voice channels. Sync channels are not switchable and must be force connected. Refer to Section 10.4, Synchronous Connections. Unless you have the optional NMS installed, you must leave one port configured for async (to access the Command Facility). PROTOCOL MENU Configure the port for sync. Select a channel protocol from the menu.
PAGE 86
Multiserver 5000 Table 9-1. Sync Protocol Options 84 Option Description 1. DLC Typical DLC protocols are SDLC and HDLC. The DLC protocol options are standard bitoriented protocols, which use Hex 7E as a block separator or idle fill, and a standard CCITT polynomial for frame-check-sequence calculations. See information on Idle Fill in Table 9-2 for specifics on AS/400® operation or IBM® 3270 SDLC half-duplex operations with an IBM 3275. 2.
PAGE 87
CHAPTER 9: Data-Channel Configuration performed after changing the port configuration to sync. Leave the menu and perform the reset, and try this procedure again. rate, channel clocking, and interface type— reference other tables in this chapter. These tables are located immediately after Table 9-3. The CHANNEL CHARACTERISTICS menu will appear. This menu differs depending on the sync protocol selected during port configuration.
PAGE 88
Multiserver 5000 Table 9-3. Sync Channel Characteristics Option Protocol Default Description Data Rate DLC ASCII Bisync EBCDIC Bisync H-P Sync RTS/CTS Sync-Pad MICOM DLC MICOM Voice Fast Packet TDM 2400 2400 2400 2400 2400 2400 2400 9600 2400 2400 Sets data rate (in bps) for the port. Note: If the Clocking Source is selected as external, the data rate must be configured the same as that of the external clocking source.
PAGE 89
CHAPTER 9: Data-Channel Configuration Table 9-3. Sync Channel Characteristics (continued) Option Protocol Default Description Interface Type DLC ASCII Bisync EBCDIC Bisync H-P Sync RTS/CTS Sync-Pad MICOM DLC MICOM Voice TDM TO DTE TO DTE TO DTE TO DTE TO DTE TO DTE TO DTE TO DTE TO DTE Set TO DTE for interfacing with data terminal equipment. The channel will return CTS on in response to RTS on from the attached terminal equipment. Set TO DCE for interfacing with data communications equipment.
PAGE 90
Multiserver 5000 Table 9-3. Sync Channel Characteristics (continued) Option Protocol Default Description Number of Leading Pad Characters* ASCII Bisync EBCDIC Bisync H-P Sync RTS/CTS Sync-Pad 1 1 1 3 1 Sets the number of leading pad characters to be transmitted at the start of the block. This is used for a time delay (1-9).
PAGE 91
CHAPTER 9: Data-Channel Configuration MICOM Voice ENABLE Table 9-3. Sync Channel Characteristics (continued) Option Protocol Default Description DSR Control DLC ASCII Bisync EBCDIC Bisync H-P Sync RTS/CTS Sync-Pad MICOM DLC MICOM Voice Fast Packet TDM NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL NORMAL When set to NORMAL, remote DTR changes to appear on the local DSR. When set to FORCED ON, remote DTR changes are ignored. The local DSR is forced on when the local DTR is on.
PAGE 92
Multiserver 5000 Table 9-5. Synchronous Clocking Configuration Description of Use Normal Synchronous or Cascade Use when DTE is co-located with Multiserver. TX and RX clocks are supplied by the Multiserver.
PAGE 93
CHAPTER 9: Data-Channel Configuration Table 9-6. CCM and 6-Channel CEM (MX215C only) Local Sync Channel Interface Configured to DTE Multiserver DTE Constant Carrier Mode Pin I/O 4 I Off-to-On transition raises CTS. 5 O 8 Controlled Carrier Mode Pin I/O Signal 4 O RTS Set on after RTS goes on. Set off when RTS goes off. 5 I CTS O Forced ON. 8 I CD 22 O 2 seconds on/4 seconds off when start ring frame received from remote unit.
PAGE 94
Multiserver 5000 Table 9-7. CCM and 6-Channel CEM (MX215C only) Local Sync Channel Interface Configured to DCE Multiserver DCE Constant Carrier Mode Pin I/O 8 O Held ON. 11 I 4 Controlled Carrier Mode Pin I/O Signal Lead output data. 4 I RTS ... Must be ON to enable data output. 5 O CTS I ... Ignored (except in RTS/CTS mode). 8 O CD 25 I Start ring frame is sent to remote when off-to-on transition is detected.
PAGE 95
CHAPTER 9: Data-Channel Configuration 9.3 Asynchronous Channels Before configuring an async channel, be sure that the port is configured for async (from the Port Configuration Menu). Ports (channels) A2 to A6 and all CEM module ports are by default async channels. You do not need to configure ports which are already async. If the port has been configured as sync or a link, then you will need to re-configure the port for async.
PAGE 96
Multiserver 5000 ASYNC CHANNEL CHARACTERISTICS The Channel Characteristics Menu is accessed from the Async Channels Menu as option 1. ASYNC CHANNEL 1 CHANNEL CHARACTERISTICS The operating parameters associated with all async terminals are set here The current configuration for each characteristic is shown in brackets, to the right of the menu option.
PAGE 97
CHAPTER 9: Data-Channel Configuration Table 9-8. Asynchronous Channel Characteristics Option Default Description 1. Data Rate 9600 Sets the data rate (in bps) for the port. It is recommended that ports attached to a host port be set for a fixed speed. (ABR=autobaud rate detection. See explanation of ABR in text.) 2. Code Level 8 Sets the bits-per-character rate for data and messages at 5, 6, 7, 8, or 9. This includes the parity bit (see Table 9-10).
PAGE 98
Multiserver 5000 Table 9-8. Asynchronous Channel Characteristics (continued) Option Default Description 7. XON Character DC1 Selects the character for the X-ON function. To ascertain which control character to select, refer to the user manual of the device attached to the port. Choices for the X-ON character are DC1, DC2, DC3, and DC4. 8. XOFF Character DC3 Selects the character for the X-OFF function.
PAGE 99
CHAPTER 9: Data-Channel Configuration Autobaud Rate Detection (ABR). The Multiserver 5000 has the capability of automatically determining the data rate of a port in the range of 50 to 19,200 bps by dynamically examining the first (sign-on) character after a connect. In addition, the Multiserver will pass the sign-on character (a carriage return) to a host computer, if the port configuration is set in the following manner: Code Level and Parity Conversion.
PAGE 100
Multiserver 5000 CHANNEL FEATURES The Channel Features Menu is accessed from the Async Channel Menu as option 2. Additional interface parameters associated with special applications are controlled by this menu. The current configuration for each menu option is displayed in brackets. Each of these features is explained in Table 9-11.To return to the previous menu (ASYNC CHANNEL Menu), enter a P. ASYNC CHANNEL 2 CHANNEL FEATURES CHANNEL FEATURES [node id/ch #] 1. PRIORITY [HIGH] 2. EIA CONTROL 3.
PAGE 101
CHAPTER 9: Data-Channel Configuration Table 9-11. Asynchronous Channel Features Option Default Description 1. Priority High Determines whether port is high or low priority in reference to other async ports. (Async channels always have lower priority than voice/fax or sync channels.) Keep the port’s setting to high priority where an interactive (terminal and host) connection needs quick response time.
PAGE 102
Multiserver 5000 disconnect the channel in the event of loss of sync on the link. Table 9-11. Asynchronous Channel Features (continued) Option Default Description 8. Command Mode Entry Sequence ^X Break There are two keying sequences available to the channel user for accessing the Command Mode. If the ^X^Y option is chosen, then both ^X^Y and ^X can be used to access the Command Mode. If ^X Break is chosen, then only ^X will access the Command Mode. 9.
PAGE 103
CHAPTER 9: Data-Channel Configuration EXTENDED FEATURES The Extended Features Menu is accessed from the Async Channel Menu as option 3. The current configuration for each menu option is displayed in brackets. Each of these features is explained in Table 9-12.To return to the previous menu (ASYNC CHANNEL Menu), enter a P. ASYNC CHANNEL 3 EXTENDED FEATURES EXTENDED FEATURES [node id/ch #] 1. DATA COMPRESSION 2.
PAGE 104
Multiserver 5000 9.4 Copy Channel Parameters By using the Copy Channel Parameters selection, you can configure a range of sync or async ports or a single port. If the next port(s) to be configured matches (or closely resembles) the one previously configured, this option can save you time. NOTE: Source and destination ports must be of a like kind (async to async, sync to sync) and protocol (sync only, DLC to DLC, TDM to TDM).
PAGE 105
CHAPTER 9: Data-Channel Configuration 9.5 Review Data-Channel Configuration ENTER NODE-ID/CHANNEL# (OR RANGE OF CHANNELS)(^X TO ABORT): REVIEWING SYNC-CHANNEL CONFIGURATION To review sync-data channels, enter the View Configuration menu. At this prompt, enter the node ID, a slash, and a sync channel or range of channels you wish to review. (Channel ranges should be in the form: starting channel, dash, ending channel. For example, channels B1 through B6 would be entered as B1B6.
PAGE 106
Multiserver 5000 REVIEWING ASYNC-CHANNEL CONFIGURATION To review async-data channels, enter the View Configuration menu. At this prompt, enter the node ID, a slash, and an async channel or range of channels you wish to review. (Channel ranges should be in the form: starting channel, dash, ending channel. For example, channels B1 through B6 would be entered as B1-B6.) COMMAND FACILITY MAIN MENU [node id] 1 After the channel (or range) has been entered, the Async Channels menu appears.
PAGE 107
CHAPTER 9: Data-Channel Configuration Async Channel Features. See Table 9-11 for information on each of the features.
PAGE 108
Multiserver 5000 10. Switching Configuration This chapter discusses switching configurations for synchronous and asynchronous data channels. Information on configuring Voice/Fax channel switching can be found in the MS1 Voice/Fax Card User’s Manual. SWITCHING CONTROL [node id] 1. DISABLE CHANNEL 2. ENABLE CHANNEL 10.1 Switching Control 3. FORCE CONNECT 4. FORCE DISCONNECT The Switching Control menu is accessed from the Command Facility Main Menu as option 5. Each option is explained in Table 11-1. 5.
PAGE 109
CHAPTER 10: Switching Configuration Table 10-1. Switching Control (continued) Option 2. Enable Channel Description This option returns an out-of-service async or voice/fax channel (or range of channels) to the idle state. When this selection is chosen, the following prompts will appear on the screen: ENTER NODE/CHANNEL# (OR RANGE OF CHANNELS)(^X TO ABORT): Enter the node ID, slash, channel (port) number or range of channels. Press .
PAGE 110
Multiserver 5000 Table 10-1. Switching Control (continued) Option 4. Force Disconnect Description Disconnects two ports which have been force-connected. This option also permits removal of a port from the queue. When this selection is chosen, the following prompt will appear on the screen: ENTER NODE/CHANNEL# (OR RANGE OF CHANNELS)(^X TO ABORT): Enter the node ID, slash, channel (port) number or range of channels. Press .
PAGE 111
CHAPTER 10: Switching Configuration 10.2 Point-to-Point Dedicated (Force Connect All) This function is designed for a single interconnect link point-to-point application (Figure 10-1). If a pair of Multiservers is to serve as strictly dedicated point-to-point multiplexors, the switching function is quite basic. Before enabling the Force Connect All function, make sure each port of the Multiserver and its matching port on the remote Multiserver have the same port configurations.
PAGE 112
Multiserver 5000 disconnecting ranges, see Section 10.3, Force Connecting a Range. 10.3 Force-Connecting a Range The procedures for force-connecting async and sync channels are the same. The two ports to be connected must be the same type of port (i.e., async to async, sync to sync, or voice to voice), although the configuration of the ports need not exactly match. If a port is force-connected, no other channel may access it through switching calls.
PAGE 113
CHAPTER 10: Switching Configuration voice-voice, async-async, sync-sync connections will be made. • Ports NEWYORK/D1 and D2 are not paired up at all, because the “from” range is greater than the “to” range. If the “from” range is greater than the “to” range, the unpaired from ports will not be connected. NOTE: If an async port within a specified range is connected to the Command Facility (via $CMD), it will not be force-connected.
PAGE 114
Multiserver 5000 10.5 Asynchronous Connections The following five methods of switching are supported for async ports: Force Connection The network operator configures a dedicated connection between two ports in the network. Fixed Destination The network operator configures the destination for the user’s channel. Class The user enters a mnemonic, configured as a class name, which is defined as one or more ports in the network. (Refer to Section 10.8, Classes, for class information.
PAGE 115
CHAPTER 10: Switching Configuration and then for an available port in the secondary class. The following steps are used to make a class connection. 1. At the ENTER CLASS prompt, enter the class name to which you wish to connect. 2. The class password prompt will appear on the screen. Enter the password. Press . 3. If the port is not available, the screen will display one of the following messages: Waiting Q=n. The ports for the class are already connected to other users, and you are in queue position n.
PAGE 116
Multiserver 5000 Note: The wild card (*) can be used to access a range of ports. To access any async port in the Multiserver identified by the name NEW_YORK, you would type the following: NEW_YORK/* 2. The CLASS PASSWORD prompt will appear on the screen. If the destination port has been configured as part of a class, enter the class password. 3. If the port is not available, the screen will display one of the following configurable dialog messages: Busy. The port is already connected to another user.
PAGE 117
CHAPTER 10: Switching Configuration 10.7 Asychronous-Channel Switching Parameters Control of async-channel switching capability is configured through the Switching Parameters menu. To access this menu, follow this menu sequence: COMMAND FACILITY MAIN MENU [node id] ENTER TO NODE-ID/CHANNEL# (^X TO ABORT): Enter the appropriate information and press . The Switching Parameters menu appears.
PAGE 118
Multiserver 5000 Table 10-2. Switching Parameters Option Default Description 1. Connect Protocol Dedicated Selects the communication protocol used. The protocol must be compatible with the attached device. There are three options: Dedicated — This option is used for terminals or computer ports which can operate on data activity only. This protocol must be used on-line driver data channels. DTR (Data Terminal Ready) — This option is used for terminals or acknowledge call requests.
PAGE 119
CHAPTER 10: Switching Configuration Table 10-2. Switching Parameters (continued) Option Default Description 7. Resource Class None This option includes the port as part of a class. The class name must already be configured before this option can be utilized. Select this option and the following prompt will appear on the screen: ENTER RESOURCE CLASS (8 CHARS MAX)(^X TO ABORT) Enter the class name (8 characters maximum). Press .
PAGE 120
Multiserver 5000 10.8 Classes WHAT IS A SWITCHING CLASS? A class is a group of one or more ports that may be used for similar purposes by network users (e.g., all ports connected to a specific application may be contained in a class). You can think of classes as hunt groups, where the user will be connected to any of the available ports in the group. The maximum number of classes per Multiserver is 64. Users can access port(s) by name, without having to know the port’s physical location in the network.
PAGE 121
CHAPTER 10: Switching Configuration FAX REMOTE OFFICES B2 PHONE CENTRAL OFFICE MULTISERVER 1000 B1 A2 A3 A4 A5 HOST FAX B6 B5 OTHER TERMINALS CONNECTED TO HOST B4 B3 B2 B2 B1 PHONE A1 A6 MULTISERVER 1000 A2 A3 ASYNC TERMINAL COMMAND FACILITY B1 A2 MULTISERVER 5000 A3 A4 A5 PHONE To C1 and C2 To D1 and D2 FAX To E1 and E2 FAX PBX MULTISERVER 1000 B2 B1 PHONE A2 A3 A4 A5 Figure 10-4. Example of a Switching Class (See the explanation on the next page).
PAGE 122
Multiserver 5000 EXAMPLE OF A SWITCHING CLASS Figure 10-4 shows a Multiserver network. The Central Office has a Multiserver 5000 with a 6-channel CEM and 3 Voice/Fax cards. This will be considered the local node. Each remote office has a Multiserver 1000 with one Voice/Fax card. In this application, the remote Voice/Fax channels will be able to reach the local PBX at all times. However, there are twelve remote data terminals (four in each office) and only six available connections to the host computer.
PAGE 123
CHAPTER 10: Switching Configuration The Class Parameters menu appears: Each of the menu options are explained in Table 10-3. To include a port as part of a class, select option 7 from the Switching Parameters Menu (see Section 10.7, Asynchronous Switching Parameters, and Table 10-2) and insert the class name. To define a class that a port automatically connects to, select option 8 from the Switching Parameters Menu (see Section 10.
PAGE 124
Multiserver 5000 Table 10-3. Class Configuration (continued) Option Default Description 3. Class Password None Password protection is available for all ports assigned to a class. If a password is assigned, the user will be prompted for the class password before being allowed to continue. After two unsuccessful password attempts, the call will be disconnected. Access to any port in the class via matrix switching is protected by the class password.
PAGE 125
CHAPTER 10: Switching Configuration Table 10-3. Class Configuration (continued) Option Default Description 5. Class No Activity Disconnect 0 The no activity feature monitors the class channel and, after a specified period of time, if there is no activity on the channel, it will be disconnected. When you select this option, the following prompt will appear: ENTER CLASS NO ACTIVITY TIMEOUT [ 0]: Type in the desired timeout period (0 = disabled, or 1 through 255 for the timeout interval in minutes).
PAGE 126
Multiserver 5000 Disconnect Sequence (Calling, Receiving, and Dual ports 10.9 Connect Protocol Details Connect protocol is option 1 of the Switching Parameters menu. There are three connect protocol options: Dedicated, Auto, and DTR. A discussion of the protocols and how to configure them is in Section 10.7, Asychronous Channel Switching Parameters, and Table 10-2. This section discusses how the call request, completion, and disconnect sequences operate for the dedicated, auto-answer, and DTR protocols.
PAGE 127
CHAPTER 10: Switching Configuration or For Dual port Idle State: DTR can be high or low. The Multiserver holds DSR, CTS, CD, and RI low. 1. Multiserver raises DSR, CTS, and CD. 2. If DTR is high, no response is required. If DTR is low, device must raise DTR within 60 seconds. 3. If ABR is enabled, then a will be forwarded. Disconnect Sequence For Dual port that is connected as a Calling port: Initiated by Multiserver (or remote end): 1. Calling device disconnects. 2.
PAGE 128
Multiserver 5000 or Disconnect Sequence Initiated by Multiserver (or remote end): Initiated by device: 1. Calling device disconnects. 1. Device drops DTR. 2. Multiserver drops CTS, DSR, and CD. 2. Multiserver drops DSR and CTS. 3. Port is marked out-of-service until device acknowledges disconnect by dropping then raising DTR. Initiated by Multiserver (or remote end): 1. Multiserver drops DSR and CTS. 2. If Call Inhibit is on, the channel will be marked out-of-service until device drops DTR.
PAGE 129
CHAPTER 10: Switching Configuration 10.11 X.21 Switching Considerations There is no special async channel configuration required for use with X.21, with the following possible exception. A special configuration is required if you are trying to connect a port on the Multiserver that requires a DTR protocol to a port on a feeder mux (configured for DTR). Even though the Multiserver can be set only for Data Activity, the port, if configured for DTR at the Connect Protocol Menu, will function as needed.
PAGE 130
Multiserver 5000 SWITCHING PARAMETERS [DENVER/A5] ENTER TO NODE-ID/CHANNEL# (^X TO ABORT): DENVER/A5 ASYNC CHANNEL 4 SWITCHING PARAMETERS SWITCHING PARAMETERS [DENVER/A5] 1 CONNECT PROTOCOL CONNECT PROTOCOL [DEDICATED] 2 DTR SWITCHING PARAMETERS [DENVER/A5] 7 RESOURCE CLASS ENTER RESOURCE CLASS (8 CHARS MAX) (^X TO ABORT): DTR 128 M MAIN MENU For additional information on configuring your port parameters, refer to Section 9.3, Asychronous Channels, and for classes, refer to Section 10.
PAGE 131
CHAPTER 10: Switching Configuration 10.12Review Switching Configuration for an Async Channel ENTER TO NODE-ID/CHANNEL# (^X TO ABORT): To review the switching parameters of async channels, enter the View Configuration Menu. COMMAND FACILITY MAIN MENU [node id] 1 At this prompt, enter a channel or range of channels (for example, DENVER/a2-a6).
PAGE 132
Multiserver 5000 11. Administration System administration can be done through the dedicated command port on the NMS module or a floating command port. This chapter assumes you are using a floating command port. 11.1 Reset A reset may be necessary to clear a channel, node, or link. The reset causes the software to return to a defined configuration. Choose the reset that is least likely to disturb the users or network. For instance, perform a channel reset to clear one channel.
PAGE 133
CHAPTER 11: Administration Banner Message Menu Functions Administration System Clear Latched Alarms System Reset Restart Link Default Configuration Reset Channel Current Configuration Key: Press Down-Arrow Key Press Right-Arrow Key Figure 11-2. Menu-flow diagram for LCD/Keypad resets. After you have entered the correct channel, press the EXEcute key. To reset to a Default or Current Configuration, press the EXEcute key at the appropriate screen.
PAGE 134
Multiserver 5000 Table 11-1. Reset Options Option Description 1. Node Disconnects the Command Facility and resets the local Multiserver node, all locally connected channels, and locally attached feeder muxes. Remote Multiservers and feeder muxes will not be reset by this option. If a port has been configured as sync or reconfigured from sync to async, or a different clocking rate has been configured, this reset is required prior to channel configuration.
PAGE 135
CHAPTER 11: Administration 11.2 The Command Mode The Command Mode is a single menu which supports configuration and testing of the local port and access to the Command Facility Main Menu. The local port is defined as the one to which the terminal you are using is connected. The Command Mode menu will appear: COMMAND MODE: CHANNEL xxx 1. ASYNC LOCAL LOOPBACK 2. LOCAL CHANNEL CONFIGURATION 3. COMMAND FACILITY MAIN MENU 4.
PAGE 136
Multiserver 5000 Table 11-2. The Command Mode Option Description 1. Async Channel Loopback A selection of loopback tests. See Section 12.3, Async Channel Loopback in the Command Mode, for a complete discussion of the tests. 2. Local Channel Configuration Provides control and modification of the locally connected port. After entering Command Mode, the terminal user may reconfigure port parameters. All changes will take effect after exiting the Command Mode.
PAGE 137
CHAPTER 11: Administration 11.3 Configuring the Command Facility The Command Facility Parameters Menu controls the system time, date, system reports, external modem (if an NMS module is installed), No Activity timeout, and the LCD Banner message. COMMAND FACILITY MAIN MENU [node id] 3 CONFIGURE LOCAL NODES If an NMS module is installed, refer to the NMS manual to configure the dedicated Command Port and the Log Port parameters.
PAGE 138
Multiserver 5000 Table 11-3. Command Facility Configuration Option 1. Time Default Description 00:00:00 The system time. At power-up, the Multiserver requests the time from locally attached feeder muxes to make sure that the network agrees on the time of day. If there are no local feeder mux units, time starts at 00:00:00. During a keypad warm reset or default value node reset, the time resets to 00:00:00.
PAGE 139
CHAPTER 11: Administration Table 11-3. Command Facility Configuration (continued) Option 6. Periodic Reporting Interval Default Description 60 Defines the interval of time for a periodic report. There are five options: None, 10, 20, 30, and 60. If None is chosen, status reports will not be output periodically. Status reports can be viewed at any time by selecting option 7 (System Statistics) of the Status/ Statistics Menu. See Section 11.9, Switching Administration, for more information. 7.
PAGE 140
Multiserver 5000 Table 11-3. Command Facility Configuration (continued) Option 8. Output Periodic Report (continued) Default Description Local Command Port Remote Node. Periodic reports are output to a remote node. If remote node is selected, the node ID must be named in option 9. If no remote node is named in option 9, the reports will be sent to the Local Command Port. The remote node will deliver the periodic reports to the output location selected in its Command Facility Parameters menu.
PAGE 141
CHAPTER 11: Administration Table 11-3. Command Facility Configuration (continued) Option 11. External Modem Phone # (continued) Default Description None Enter the characters in the order you would have them executed.
PAGE 142
Multiserver 5000 11.4 Messages ALARM MESSAGES Alarms generally indicate that an error has been detected that impacts or degrades the performance for part of the network. For example, an alarm message would be sent if the line error rates were excessive, or if a link went down. To clear an alarm, select option 9 (Clear Alarm Displays) from the Command Facility Main Menu or COMMAND FACILITY MAIN MENU [node id] 9 CLEAR ALARM DISPLAYS select Clear Latched Alarms on the LCD/Keypad.
PAGE 143
CHAPTER 11: Administration will accept the entry, and the following prompt appears: Enter up to 45 characters, including spaces and punctuation. Special rules apply when entering the ENTER MESSAGE (45 CHARACTERS MAX, ^X TO ABORT): Table 11-4. Special Message Characters Desired Character in Message What to Input ^X ^x Without the key, ^X will abort the process (escape) To include an escape in the text, it must be preceded by an .
PAGE 144
Multiserver 5000 Special rules apply when entering the characters listed in Table 11-4 in a dialog message. Length: Dialog Messages vary in maximum length. Syntax: Alphanumeric characters (A to Z, 0 to 9), spaces, and all symbols may be used. Messages are not case-sensitive. All dialog messages can be quickly reviewed through the View Configuration menu. Table 11-5. Dialog Messages Default Max Char 1.
PAGE 145
CHAPTER 11: Administration Table 11-5. Dialog Messages (continued) Default Max Char 11. Unassigned UNASSIGNED 17 Sent when a node, class, or port is unknown in the network. It could also mean that a password for the class may be incorrect. (This message generally indicates a typing or configuration problem.) 12. Incompatible INCOMPATIBLE 17 Sent when any connection is attempted that is not compatible with the configuration. 13.
PAGE 146
Multiserver 5000 11.5 Network Security Protecting selected portions of the Command Mode and the Command Facility involves two types of security: password protection and lock-out configuration. PASSWORDS Passwords are security protection for the Multiserver. Four types of password protection can be assigned to the Multiserver unit: Command Facility, Channel, Class, and LCD/Keypad. Channel and Class passwords can be displayed from the Command Facility.
PAGE 147
CHAPTER 11: Administration Table 11-6. The Password Menu Option 1. Global Description This password provides access to all functions. To set the password, select this option. The following prompt appears: ENTER GLOBAL PASSWORD (^X TO ABORT): Enter the password. Press . The screen will return to the Password menu. To abort the process, press ^X. 2. Status This password provides access to view, status, and exit Command Facility functions. To set the password, select this option.
PAGE 148
Multiserver 5000 11.6 Status/Statistics Status and statistics reports are available on the Status/Statistics Menu. Status is a snapshot of the system as it appears the moment the request is made; statistics are a readout of the system within a defined period of time. You will use the Status/Statistics menu often to monitor your network’s operation. To access the Status/Statistics Menu, select option 2 on the Command Facility Main Menu. COMMAND FACILITY MAIN MENU [node id] 2 STATUS/STATISTICS [node id] 1.
PAGE 149
CHAPTER 11: Administration Table 11-7. Status/Statistics (continued) Option Description 2.
PAGE 150
Multiserver 5000 Table 11-7. Status/Statistics (continued) Option 4. Queue Status Description Lists all the class numbers, class names, and the node ID/channel of the ports queued to each class. This will display up to 30 ports per class. All 64 classes will display, whether or not they are configured.
PAGE 151
CHAPTER 11: Administration 5. Voice/Fax Status If the Multiserver is equipped with a voice/fax module, this option will display a range of ports selected, the input level, the mode (on hook, off hook, busy), the software revision, and, if applicable, the test mode and test status. When this options is selected, the following prompt appears: ENTER NODE-ID/CHANNEL # (OR RANGE OF CHANNELS)(^X TO ABORT): Enter the node ID, a slash, and the channel number (or range of channels). Press .
PAGE 152
Multiserver 5000 Table 11-7. Status/Statistics (continued) Option Description 7. System Statistics Provides two options: the period report (the report compiled during the last reporting period) or a demand report (a snapshot of the system at the time of request).
PAGE 153
CHAPTER 11: Administration Table 11-7. Status/Statistics (continued) Option Description System status is displayed as a set of statistics in a single report. The statistics reflect system activities that have occurred since the last reporting interval. (If no reporting period is defined in the Command Facility Parameters Menu, statistics are reset every 60 minutes.
PAGE 154
Multiserver 5000 7. System Statistics (continued) The Mux Link and the X.21 Link: [node id] CONNECT STATISTICS CONNECT MAXIMUM CLASS NAME CONNECTS FAILURES IN QUEUE --------------------------------------------------------------01 xxxxxxxx 2 0 0 02 xxxxxxxx 7 0 1 03 xxxxxxxx 5 0 0 04 xxxxxxxx 23 3 4 05 xxxxxxxx 2 0 0 63 64 CURRENT CONNECTS: 12 ENTER CARRIAGE RETURN TO CONTINUE 152 CLASS The number of a specific class. NAME The configured name of a specific class. CONNECTS The number of connects.
PAGE 155
CHAPTER 11: Administration Table 11-7.
PAGE 156
Multiserver 5000 11.7 Link Administration RESET If a link is not working properly (interconnect, mux, or X.21), it can be reset. If the other end of the link is a feeder mux, the mux will also reset. All channels currently using the link will experience a temporary interruption. See Section 11.1, Reset, and Table 11-1 for more information on this procedure. STATUS/STATISTICS The following options of the Status/Statistics Menu provide link information: Option Description 1.
PAGE 157
CHAPTER 11: Administration 11.9 Switching Administration Monitoring the switching functions of your network is critical for high-efficiency network performance. Most of the information you need is with the Status/Statistics menu. The following options of the Status/Statistics Menu provide switching information: Option Description 1. Channel Status Lists data channels and to what node/channel they are connected. 4. Queue Status Lists all switching classes and what data channels are in queue.
PAGE 158
Multiserver 5000 Table 11-7. Status/Statistics (continued) Option 8. Channel Statistics Description Channel Statistics are part of the System Statistics (see option 7 above). When this option is chosen, the current channel statistics for the node are displayed. Voice channels and integral devices are not displayed with this menu. Select this option and the following prompt appears: ENTER NODE-ID (^X TO ABORT): Enter the node ID. Press . A demand report of the Channel Statistics is displayed.
PAGE 159
CHAPTER 12: Diagnostics 12. Diagnostics 12.1 Self-Test The self-test checks the operation of all system memory. The Multiserver automatically executes a self-test when power is first turned on or when the system is reset. All LED indicators turn ON and the Multiserver does a RAM and ROM check. The port indicators stay ON until the completion of the selftest. When the test is complete, the LCD will display either SELF TEST PASSED or the appropriate alarm message.
PAGE 160
Multiserver 5000 LOCAL FOX FOX INITIATING TERMINAL MULTISERVER When this test is accessed, the Multiserver continually outputs a fox message to the testing terminal (Figure 12-1). The fox message should read THE QUICK BROWN FOX JUMPS OVER THE LAZY DOG. 1234567890. It contains every English alphanumeric symbol. The integrity of the port and the terminal may be judged by the quality of the returned fox message.
PAGE 161
CHAPTER 12: Diagnostics 12.4 System Diagnostics in the Command Facility The system administrator may perform all of the following diagnostics from the Command Facility. Some of the tests may also be performed at the LCD/Keypad. Section 13.6, Diagnostics, explains each of the diagnostic functions that can be performed with the LCD/Keypad. The Diagnostic Menu of the Command Facility is accessed as option 7 from the Command Facility Main Menu.
PAGE 162
Multiserver 5000 COMMAND FACILITY TERMINAL DATA INPUT HERE. 1 REMOTE TERMINAL MODEM FOX MODEM FEEDER MUX 2 LOCAL MULTISERVER LOCAL TERMINAL LEGEND: FOX TEST (ONLY ONE LOCAL OR REMOTE NODE/CHANNEL MAY BE SELECTED). INPUT MESSAGE (ONLY ONE LOCAL OR REMOTE NODE/CHANNEL MAY BE SELECTED). INPUT DATA APPEARS ON COMMAND FACILITY SCREEN. FOX FOX MESSAGE GENERATOR 1 THE REMOTE TEST OUTPUTS TO A REMOTE TERMINAL. 2 THE LOCAL TEST OUTPUTS TO THE LOCAL TERMINAL. Figure 12-3. Async Channel Output.
PAGE 163
CHAPTER 12: Diagnostics COMMAND FACILITY INITIATES TEST. ASYNC CHANNEL OUTPUT 1. FOX 2. INPUT CR - ACCEPT ENTRY M - MAIN MENU TEST DOES NOT GO OVER THE LINK. * ATTACHED DEVICE LOCAL MULTISERVER GENERATES TEST DATA. ENTRY: LEGEND: DATA FLOW * ATTACHED DEVICE MUST BE CONFIGURED SO THAT IT CAN The Fox Message Test causes a continuous fox message to be output to the test port. The port that is being tested will not be able to accept any other instructions as long as the test continues.
PAGE 164
Multiserver 5000 The following menu will appear: SYNC CHANNEL LOOPBACK [TERMINATE LOOPBACK] 1. INITIATE LOOPBACK 2. TERMINATE LOOPBACK CR - ACCEPT ENTRY M - MAIN MENU ENTRY: After the test is initiated, the Command Facility terminal will be returned to the Command Facility main menu. On the attached synchronous device, all characters entered will be echoed back to itself. Integrity of the port and the terminal may be judged by observing the quality of the returned data.
PAGE 165
CHAPTER 12: Diagnostics 12.5 Testing the Network In a Multiserver network, there are several loopback and test-pattern tests that you can use to diagnose the integrity of various segments of the network. The modules in a Multiserver have diagnostic tests initiated by those units; detailed information on each of those tests is in the individual module manuals.
PAGE 166
Multiserver 5000 3. You may do either one of the following setups: a. • Select remote echo (option 2). • Attach an async tester (i.e., a BERT) to the async port initiating the test. Type in some data. All data entered should be received on your display. • Type in some data. All data entered should be received on your display. or b. Select the remote fox (option 4). The message is automatically sent. It should be received and displayed. or b. Select the remote fox (option 4).
PAGE 167
CHAPTER 13: LCD/Keypad 13. LCD/Keypad 13.1 General LCD/Keypad Information The Multiserver 5000 has an LCD (Liquid Crystal Display) and a keypad on the front of the unit. The 80-character LCD consists of two 40-character lines. The LCD is used to display status and alarm messages, as well as diagnostic and minimal configuration menus. When you turn on the Multiserver, the LCD will display the banner message, the current system time, a current alarm or event (if any), and its time.
PAGE 168
Multiserver 5000 LCD BLINKING BACKLIGHT When working in the menus, should the backlight begin blinking, it means that there is an alarm message. You can exit to the top level (Banner Message Display) and read the message or just clear the blinking backlight. This is how to clear the blinking backlight: From the Banner Message Display, press the right arrow, then press the down arrow three times. The display will read Clear Latched Alarm. Press the EXEcute key and the blinking will stop.
PAGE 169
Local Node ID System Reset Default Configuration Clear Latched Alarms Reset Channel Current Configuration Restart Link Sync Channel Loopback System Controlled Reset Channel Forced On Busy Mode Forced Off Remote Composite Loopback Terminate Test Monitor Channel Interface Signals LED Test Self Test Local Loop Input Level Display Terminate Test Integral Devices Local Loopback Digital Loopback ISU Local Loopback with TP Terminate Test Hardware Overview Section 13.
PAGE 170
Multiserver 5000 EXE Move cursor to the left Abort process, move to previous menu Current Time Banner Message Denver 8:49:03 Time when alarm/ event occurred 11:35:47 Local Link reset A1 Alarm/Event Message Figure 13-3. The LCD Banner Display. Increment letter/number by one (If key is held, the character will increment rapidly.) Move cursor to the right EXE Accepts entry CHANNEL NUMBERS When the LCD display requests you for a channel number, use the following keys as shown.
PAGE 171
CHAPTER 13: LCD/Keypad CONFIGURING THE BANNER MESSAGE The factory default message for the LCD is Name Your Node. This message can be customized at an async terminal operating in the Command Facility. Follow these procedures: At this prompt, enter the LCD Banner Message. The message may be a maximum of 20 characters and can contain any displayable characters Review System Message Log Menu Functions 13.
PAGE 172
Multiserver 5000 VOICE/FAX If a voice/fax module is installed, this menu offers the following two options: Option with a letter (no numbers or underscores) and must not contain Menu Functions Description Reset Channel Resets the selected voice/fax channel. Busy Mode Controls how the busyout state of the channel is determined.
PAGE 173
CHAPTER 13: LCD/Keypad Press Key Resulting Display Node name: [!240] The space can be used to delete existing characters in columns that will be blank. (For example, if the !240 node ID becomes NY, the last two columns must be blank.) The node number appears in the brackets. (The number shown above in the brackets is the default node number.) The cursor will be in the farthest numeric position to the right.
PAGE 174
Multiserver 5000 This menu offers the following test options: Option Sync Channel Loopback Description Causes a sync port to be placed in local echo loopback similar to the async echo. WARNING: This test will interrupt all channels connected across the link. Remote Composite Loopback Sets up the unit to expect its own databack. This function is required for tests intiated by external communication devices (modem or CSU/DSU) or telco.
PAGE 175
CHAPTER 13: LCD/Keypad CHANNEL 2 OK LO RO LS CHANNEL 1 RS TM OK LO RO LS RS TM +1 dB + -4 dBm THROUGH +1 dBm -15 dBm THROUGH -5 dBm -25 dBm THROUGH -16 dBm < -25 dBm LEGEND: = ON = OFF = GREEN LIGHT NORMAL = 2 LIGHTS ON. IF CONVERSATION IS GOING ON, THIRD LIGHT IS FLICKERING. Figure 13.5. Voice/Fax Input Level Display Diagnostic Test.
PAGE 176
Multiserver 5000 Display Terminate Test voice/fax signal. The indicator lights on the voice/fax module show the level (see Figure 13.5). When this test is initiated, the display will read [Active]. Terminates all the tests initiated at this menu. Once a test is initiated, an [Active] message is displayed on the LCD. All tests remain active until terminated with Terminate Test.
PAGE 177
Appendix A: Worksheets Appendix A: Worksheets This section of the manual contains worksheets to help you organize and keep a record of your network and of your asynchronous and synchronous channel configurations. Copy these sheets as many times as necessary (keep these blank originals to make future copies). Keep a completed copy of these sheets near your Multiserver(s). The following worksheets are provided: • Worksheet for Planning Node Numbers and Node IDs (p.
PAGE 178
Multiserver 5000 Worksheet for Planning Node Numbers and Node IDs PORT A1 Node # NODE ID A2 Node # NODE ID Node # A3 NODE ID Node # NODE ID A4 Node # NODE ID A5 Node # NODE ID 176
PAGE 179
Appendix A: Worksheets Worksheet for Recording Optional Modules and their Connectors Remote CCM Local CCM CCM CCM 177
PAGE 180
Multiserver 5000 Synchronous Protocol and Channel Worksheet NODE ID (name) Channel Number Protocol Data Rate Channel Max. Clocking Transmit Block Size Max. Receive Block Size Interface Type Carrier Mode Sync Char.
PAGE 181
Appendix A: Worksheets Synchronous Protocol and Channel Worksheet (continued) NODE ID (name) continued from Number of Leading Syncs Pad Char. Number Number Encoding of of Leading Trailing Pad Chars. Pad Chars. Idle Fill Buffer Control Clock Flow Control DSR Ctrl.
PAGE 182
Multiserver 5000 Asynchronous Channel Characteristics Worksheet NODE ID (name) Channel Number Data Rate Code Level Parity Stop Bits Echo To Host/ To Terminal continued on facing page → 180
PAGE 183
Appendix A: Worksheets Asynchronous Channel Characteristics Worksheet (continued) NODE ID (name) X-ON Char. X-OFF Char. Buffer Ctrl. Flow Ctrl.
PAGE 184
Multiserver 5000 Asynchronous Channel Features Worksheet NODE ID (name) Channel Number Priority EIA Ctrl.
PAGE 185
Appendix A: Worksheets Asynchronous Channel Features Worksheet (continued) NODE ID (name) Sync Loss Disconnect Command Mode Entry Sequence Command Mode Access Command Facility Main Menu Access Local Channel Configuration continued from ← facing page 183
PAGE 186
Multiserver 5000 Asynchronous Channel Extended Features Worksheet NODE ID (name) Channel Number 184 Data Compression Remote CTS Control
PAGE 187
Appendix A: Worksheets Record of Asynchronous Classes NODE ID (name) Channel Number Class Name Secondary Class Class Password (record here and in the Password Table) Class Message Class Number Activity Timeout 185
PAGE 188
Multiserver 5000 Switching Parameters Worksheet NODE ID (name) Option Connect Protocol Unbalanced Rates Call Inhibit Receive Inhibit Character Set Matrix Switching Resource Class Destination Node/Class Channel Password 186 Entry
PAGE 189
Appendix A: Worksheets Command Facility Parameters Worksheet NODE ID (name) Option Entry Event Reporting Alarm Reporting Switch Statistics Reporting Periodic Reporting Interval Output Event/Alarm Reports Output Periodic Report Remote Node ID External Modem Priority External Modem Phone # External Alarm No Activity Timeout LCD Banner Message 187
PAGE 190
Multiserver 5000 Display Messages Worksheet NODE ID (name) Option Channel Password Welcome Class Request Class Password Connected Queue Busy Disconnected Now Answer Unavailable Unassigned Incompatible Call in Progress 188 Entry
PAGE 191
Appendix A: Worksheets Voice/Fax Parameters Worksheet NODE ID (name) Option Entry Mode Digitizing Rate Input Level Gain Output Level Attenuation Busyout Mode Bandwidth Background Priority Number of Rings Signalling Format Analog Operation Ringing Frequency Number of Digits 189
PAGE 192
Multiserver 5000 Record of Passwords NODE ID (name) Option Entry Global Status LCD/Keypad Class Number Class Name Class Password Node ID Channel Number User Channel Password 190
PAGE 193
Appendix B: Cabling Diagrams Appendix B: Cabling Diagrams This appendix contains cabling diagrams for the following: • Cabling for the CCM and 6-Channel CEMs (p. 192) • Cabling for the 12-Channel CEM (p. 198) • Cabling for the 12-Channel CEM with Line Drivers (p. 202) • Cabling for the MS1 56K CSU/DSU Module (p. 204) • Cabling for the NMS Module (p. 205) • Cabling for Converters (p. 206) • Cabling for Use with Tandem (p.
PAGE 194
Multiserver 5000 Cabling for the CCM and 6-Channel CEMs 6-CHANNEL CEM CCM DB25 PIN ASSIGNMENTS PIN 13 DCE PIN 25 DB25 (RS-232) 192 PIN 1 1 2 3 4 5 6 7 8 11 15 17 18 20 22 24 25 PROTECTIVE GROUND TX DATA RX DATA RTS (REQUEST-TO-SEND) CTS (CLEAR-TO-SEND) DSR (DATA SET READY SIGNAL GROUND CD (CARRIER DETECT) UNASSIGNED TX CLOCK RX CLOCK EXTERNAL RX CLOCK DTR (DATA TERMINAL READY) RI (RING INDICATOR) EXTERNAL TX CLOCK BUSY
PAGE 195
Appendix B: Cabling Diagrams Cabling for the CCM and 6-Channel CEMs (continued) PIN 1 25-PIN CONNECTOR (MALE) 25-PIN CONNECTOR (MALE) PROTECTIVE GROUND 1 1 TRANSMIT DATA 2 2 RECEIVE DATA 3 3 REQUEST-TO-SEND 4 4 CLEAR-TO-SEND 5 5 DATA SET READY 6 6 SIGNAL GROUND 7 7 CARRIER DETECT 8 8 UNASSIGNED 11 11 TRANSMIT CLOCK 15 15 RECEIVE CLOCK 17 17 EXTERNAL RECEIVE CLOCK 18 18 DATA TERMINAL READY 20 20 RING INDICATOR 22 22 EXTERNAL TRANSMIT CLOCK 24 24 BUSY 25 25 T
PAGE 196
Multiserver 5000 Cabling for the CCM and 6-Channel CEMs (continued) PIN 1 25-PIN CONNECTOR (MALE) 25-PIN CONNECTOR (MALE) PROTECTIVE GROUND 1 1 TRANSMIT DATA 2 3 RECEIVE DATA 3 2 REQUEST-TO-SEND 4 8 CLEAR-TO-SEND 5 11 DATA SET READY 6 20 SIGNAL GROUND 7 7 CARRIER DETECT 8 4 UNASSIGNED 11 5 TRANSMIT CLOCK 15 18 RECEIVE CLOCK 17 24 EXTERNAL RECEIVE CLOCK 18 15 DATA TERMINAL READY 20 6 RING INDICATOR 22 25 EXTERNAL TRANSMIT CLOCK 24 17 BUSY 25 22 TO MULTISERVE
PAGE 197
Appendix B: Cabling Diagrams Cabling for the CCM and 6-Channel CEMs (continued) PIN 1 25-PIN CONNECTOR (MALE) 25-PIN CONNECTOR (FEMALE) PROTECTIVE GROUND 1 1 TRANSMIT DATA 2 3 RECEIVE DATA 3 2 REQUEST-TO-SEND 4 8 CLEAR-TO-SEND 5 11 DATA SET READY 6 20 SIGNAL GROUND 7 7 CARRIER DETECT 8 4 UNASSIGNED 11 5 TRANSMIT CLOCK 15 18 RECEIVE CLOCK 17 24 EXTERNAL RECEIVE CLOCK 18 15 DATA TERMINAL READY 20 6 RING INDICATOR 22 25 EXTERNAL TRANSMIT CLOCK 24 17 BUSY 25 22
PAGE 198
Multiserver 5000 Cabling for the CCM and 6-Channel CEMs (continued) PIN 1 25-PIN CONNECTOR (MALE) 25-PIN CONNECTOR (FEMALE) PROTECTIVE GROUND 1 1 TRANSMIT DATA 2 2 RECEIVE DATA 3 3 REQUEST-TO-SEND 4 4 CLEAR-TO-SEND 5 5 DATA SET READY 6 6 SIGNAL GROUND 7 7 CARRIER DETECT 8 8 UNASSIGNED 11 11 TRANSMIT CLOCK 15 15 RECEIVE CLOCK 17 17 EXTERNAL RECEIVE CLOCK 18 18 DATA TERMINAL READY 20 20 RING INDICATOR 22 22 EXTERNAL TRANSMIT CLOCK 24 24 BUSY 25 25 TO MULTISER
PAGE 199
Appendix B: Cabling Diagrams Cabling for the CCM and 6-Channel CEMs (continued) PIN 1 DB25 MALE P1 DB25 MALE P2 TD 2 3 RD RD 3 2 TD CTS 5 4 RTS DSR 6 20 DTR GND 7 7 GND UNASSIGNED 11 5 CTS RX CLOCK 18 15 DTR 20 6 EXTERNAL TX CLOCK 24 17 RX CLOCK BUSY 25 22 RI TO MULTISERVER TX CLOCK DSR TO X.21 BIS LINE TERMINALS Figure B-5. X.21 bis Line Terminator and Composite Cable.
PAGE 200
Multiserver 5000 Cabling for the 12-Channel CEM 12-CHANNEL CEM (DCE) PIN 1 RJ-45 198 RJ-45 PIN ASSIGNMENTS 1 RING 2 RLSD 3 DTR 4 GND 5 RXD (DATA OUT) 6 TXD (DATA IN) 7 CTS 8 RTS
PAGE 201
Appendix B: Cabling Diagrams Cabling for the 12-Channel CEM (continued) PIN 1 RJ-45 25-PIN CONNECTOR (MALE) 1 22 RI 2 8 RLSD 3 20 DTR 4 7 GND 5 3 RxD 6 2 TxD 7 5 CTS 8 4 RTS TO MULTISERVER TO DTE Figure B-6. To DTE, Straight Cable Adapter (EZ419-0015).
PAGE 202
Multiserver 5000 Cabling for the 12-Channel CEM (continued) PIN 1 RJ-45 25-PIN CONNECTOR (MALE) RI 1 25 BUSY RLSD 2 4 RTS DTR 3 6 DSR GND 4 7 GND RxD 5 2 TxD TxD 6 3 RxD CTS 7 11 UNASSIGNED RTS 8 8 RLSD TO MULTISERVER TO DCE Figure B-7. To DCE, Crossover Cable Adapter (EZ420-0015).
PAGE 203
Appendix B: Cabling Diagrams Cabling for the 12-Channel CEM (continued) PIN 1 RJ-45 25-PIN CONNECTOR (FEMALE) 1 22 RI 2 8 RLSD 3 20 DTR 4 7 GND 5 3 RxD 6 2 TxD 7 5 CTS 8 4 TO MULTISERVER TO DTE RTS Figure B-8. To DTE, Straight Cable Adapter (EZ421-0015).
PAGE 204
Multiserver 5000 Cabling for the 12-Channel CEM with Line Drivers 12-CHANNEL CEM WITH LINE DRIVER (DCE) PIN 1 RS-422 RJ-45 PIN ASSIGNMENTS RJ-45 CUSTOMER EQUIPMENT 1 2 TX+ TXRXRX+ 3 4 5 6 BLACK RED GREEN YELLOW RX+ RXTXTX+ 7 8 RS-423 RJ-45 PIN ASSIGNMENTS CUSTOMER EQUIPMENT 1 2 TX+ (DATA IN) 3 TX- 4 RX- 5 RX+ 6 7 8 202 BLACK RED GREEN YELLOW RX+ RXTXTX+
PAGE 205
Appendix B: Cabling Diagrams Cabling for the 12-Channel CEM with Line Drivers (continued) RJ-45 RJ-45 1 1 2 2 TX+ 3 3 TX- 4 4 RX- 5 5 RX+ 6 6 7 7 8 8 TO MULTISERVER DTE ADAPTER Figure B-9. Straight Cable for 12-Channel Expansion Module with Line Driver (EL08MS).
PAGE 206
Multiserver 5000 Cabling for the MS1 56K CSU/DSU Module RJ-48 CONNECTOR E CSU/DSU D VOICE CHANNEL 1 KTS OPX KTS OPX VOICE CHANNEL 2 SB M E SG R1 T1 R T SB M E SG R1 T1 R T C B 1 2 1 3 4 2 5 6 3 7 4 8 9 5 10 11 12 6 A LEAVE A1 EMPTY RJ-48 AT BOTH ENDS OF CABLE PIN 1 RJ-48 PIN 8 RJ-48 PIN ASSIGNMENTS R1 1 T1 2 3 4 5 6 204 T 7 R 8 56K DIGITAL NETWORK
PAGE 207
Appendix B: Cabling Diagrams Cabling for the NMS Module NMS PIN 13 PIN 1 DCE RS-232 PIN 25 NO C NC GND GROUND (PIN 1) DB25 (MALE) NORMALLY CLOSED COMMON NORMALLY OPEN DB25 PIN ASSIGNMENTS 1 2 3 4 5 6 7 8 11 20 22 24 25 PROTECTIVE GROUND TX DATA RX DATA RTS (REQUEST-TO-SEND) CTS (CLEAR-TO-SEND) DSR (DATA SET READY SIGNAL GROUND CD (CARRIER DETECT) UNASSIGNED DTR (DATA TERMINAL READY) RI (RING INDICATOR) EXTERNAL TX CLOCK BUSY 205
PAGE 208
Multiserver 5000 Cabling for Converters E D VOICE CHANNEL 1 KTS OPX KTS OPX VOICE CHANNEL 2 SB M E SG R1 T1 R T SB M E SG R1 T1 R T C B DB25 (RS-232) DCE CONVERTER 206 1 1 2 3 2 4 5 3 6 7 4 8 9 5 10 11 12 6 A
PAGE 209
Appendix B: Cabling Diagrams Cabling for Converters (continued) V.35 CONVERTER CONNECTS TO MULTISERVER PIN 1 DB25 CONNECTOR P1 (MALE) V.35 CONNECTOR P2 (MALE) 3 P SEND DATA A 4 S SEND DATA B 19 Y SER. CLK. TX A 18 a SER. CLK. TX B 2 R RCV. DATA A 1 T RCV. DATA B 24 V SER. CLK. RCV A 23 X SER. CLK. RCV B 17 U SER. CLK. TX. EXT A 16 W SER. CLK. TX.
PAGE 210
Multiserver 5000 Cabling for Converters (continued) V.35 CONVERTER CONNECTS TO MULTISERVER PIN 1 DB25 CONNECTOR P1 (MALE) V.35 CONNECTOR P2 (FEMALE) 2 P SEND DATA A 1 S SEND DATA B 15 Y SER. CLK. TX A 14 a SER. CLK. TX B 3 R RCV. DATA A 4 T RCV. DATA B 17 V SER. CLK. RCV A 16 X SER. CLK. RCV B 24 U SER. CLK. TX. EXT A 23 W SER. CLK. TX. EXT B 6 E DSR 20 H DTR 13 C RTS 5 D CTS 8 F RLSD 22 J RING INDICATOR 25 K LOCAL TEST 7 B SIGNAL GND TO V.
PAGE 211
Appendix B: Cabling Diagrams Cabling for Converters (continued) X.21 CONVERTER CONNECTS TO MULTISERVER PIN 1 DB15 CONNECTOR P1 (FEMALE) DB15 CONNECTOR P2 (MALE) T (A) 2 2 T (A) T (B) 9 9 T (B) R (A) 4 4 R (A) R (B) 11 11 R (B) C (A) 3 3 C (A) C (B) 10 10 C (B) I (A) 5 5 I (A) I (B) 12 12 I (B) S (A) 6 6 S (A) S (B) 13 13 S (B) SIGNAL GND 8 8 SIGNAL GND SHIELD 1 1 SHIELD TO X.21 CONVERTER TO DTE INTERFACE Figure B-12. X.
PAGE 212
Multiserver 5000 Cabling for Use with Tandem 25-PIN CONNECTOR (MALE) 25-PIN CONNECTOR (FEMALE) 1 1 NOT USED 2 2 TRANSMITTED DATA 3 3 RECEIVED DATA 4 4 REQUEST-TO-SEND 5 5 CLEAR-TO-SEND 6 DATA SET READY 6 12 T-PAUSE 7 7 GROUND 8 8 DATA CARRIER DETECT 20 20 DATA TERMINAL READY 22 22 RING ADAPTER 25 25 BUSY TO MULTISERVER CONNECTS TO TANDEM CPU Figure B-13. Tandem Cable Diagram.
PAGE 213
Appendix C: Defaults Appendix C: Defaults System Administration Multiserver and Feeder Mux Default Node Numbers and IDs Unit Default Node Number Default Node ID 1000 5000 240 240 !240 !240 Mux Connected to Port A1 A2 A3 A4 A5 241 242 243 244 245 !241 !242 !243 !244 !245 Multiservers: Feeder Muxes: Port Configuration Menu Item Default Port A1..................................................................................Interconnect Link All others............................................
PAGE 214
Multiserver 5000 System Administration (continued) Command Facility Parameters Menu Item Default Event Reporting....................................................................Off Alarm Reporting....................................................................On Switch Statistics Reporting...................................................On Periodic Reporting Interval ...................................................60 (minutes) Output Event/Alarm Reports ........................................
PAGE 215
Appendix C: Defaults Asynchronous Channel Configuration Channel Characteristics Menu Item Default Data Rate .............................................................................9600 bps Code Level ...........................................................................8 Parity: If Code Level is 5 to 8 .............................................None If Code Level is 9.....................................................Odd Stop Bits .............................................................
PAGE 216
Multiserver 5000 Synchronous Channel Configuration Channel Characteristics Menu Item Default Sync Protocol .......................................................................DLC DLC Data Rate .............................................................................2400 bps Channel Clocking .................................................................TX-Internal/RX-Internal Maximum Transmit Block Size.............................................512 Maximum Receive Block Size...................
PAGE 217
Appendix C: Defaults Synchronous Channel Configuration (continued) RTS/CTS Menu Item Default Data Rate .............................................................................2400 bps Channel Clocking .................................................................TX-Internal/RX-Internal Maximum Transmit Block Size.............................................512 Maximum Receive Block Size..............................................512 Interface Type.................................................
PAGE 218
Multiserver 5000 Synchronous Channel Configuration (continued) H-P Sync Menu Item Default Data Rate .............................................................................2400 bps Channel Clocking .................................................................TX-Internal/RX-Internal Maximum Transmit Block Size.............................................9876 Maximum Receive Block Size..............................................9876 Interface Type..................................................
PAGE 219
Appendix C: Defaults Synchronous Channel Configuration (continued) TDM Menu Item Default Data Rate .............................................................................2400 bps Channel Clocking .................................................................TX-Internal/RX-Internal Interface Type.......................................................................To DTE Sync Character.....................................................................FF (hex) DSR Control .......................
PAGE 220
Multiserver 5000 Voice/Fax Module KTS Interface Menu Item Default Mode.....................................................................................Voice/Fax Digitizing Rate ......................................................................8000 Input Level Gain ...................................................................0 dB Output Level Attenuation......................................................0 dB Busyout Mode.....................................................................
PAGE 221
Appendix C: Defaults Voice/Fax Module (continued) Voice/Fax Node Parameters Menu Item Default Number of Digits (for extension numbers) ...........................2 Voice/Fax Switching Parameters Call Inhibit .............................................................................No Receive Inhibit ......................................................................
PAGE 222
Multiserver 5000 NMS Module Command Port Menu Item Default Data Rate .............................................................................ABR Code Level ...........................................................................8 Parity.....................................................................................Auto Stop Bits ...............................................................................1 Echo.................................................................................
PAGE 223
Appendix D: Messages Appendix D: Messages The messages are divided into two categories, screen display messages and LCD messages. Included in these lists are messages received from all the optional modules. Screen Display Messages MESSAGE TYPE: Alarm Vital to the system’s operation; may cause an interruption to that operation. Event Occurs in the regular operation of the system; most likely will not affect the system’s operation. Dialog Configurable async user messages.
PAGE 224
Multiserver 5000 Screen Display Messages Message ni ADB PROCESS ABORTED LINK # ci Message Type Event Explanation An attempt to place a call on the dial lines has failed. This message is displayed by the call originating modem. Info In trying to configure an Integral LAN module, you have selected a module location which does not support RTS functionality. (Most likely there is a bridge-only product installed in the module location you selected. This does not require the configure menu.
PAGE 225
Appendix D: Messages Screen Display Messages Message Message Type Explanation CHANNEL NOT INSTALLED Info An attempt has been made to configure or test a voice/fax port and the port number selected is not a voice/fax port. CHANNEL(S) NOT INSTALLED Info An attempt has been made to view the status or configuration of a range of ports that are not voice/fax ports. CHANNEL REQUEST UNSUCCESSFUL, PLEASE RETRY Info The voice/fax port you are trying to test is not working properly.
PAGE 226
Multiserver 5000 Screen Display Messages Message Message Type Explanation CONNECT FAIL MATRIX n/c Event The matrix connection request made by the local port did not complete successfully. Also, the password may be incorrect. Dialog This message is sent to the async user when a connection has been established across the link. An L or H may appear at the end if there are unbalanced rates.
PAGE 227
Appendix D: Messages Screen Display Messages Message ni DIALING TX SECONDARY LINK # ci ni DIAL LINE DROPPED LINK ci DISABLED Message Type Info Event Info Explanation The modem is dialing the secondary TX dial line number. This usually indicates that the call to the primary TX number cannot be completed (the number is busy, no answer, etc.). This message is displayed by the call-originating modem. The dial line is dropped because of bad lines, DTR dropped, or RLSD lost. This function is disabled.
PAGE 228
Multiserver 5000 Screen Display Messages Message Message Type INCOMPATIBLE LINK TYPES Info You are trying to connect a mux link to the port configured as an interconnect link or vice versa.
PAGE 229
Appendix D: Messages Screen Display Messages Message Message Type Explanation ISU LOCAL LOOPBACK ACTIVE LINK # ci Diagnostic The ISU on link ci has been placed in local loopback. ISU LOCAL LOOPBACK WITH TP ACTIVE LINK # ci Diagnostic This test puts the local ISU on link ci in loopback, then verifies the operation of the ISU by sending and receiving the test pattern. ISU TEST PATTERN ACTIVE LINK # ci Diagnostic The test-pattern generator on the ISU on link ci has been activated.
PAGE 230
Multiserver 5000 Screen Display Messages Message Message Type Explanation LOCAL DIGITAL LOOP LINK # ci LOCAL DTE LOOP LINK # ci Diagnostic LOCAL FOX Diagnostic The port is in a local fox loopback test. ni LOCAL LINK RESTART ci Event Node ni on link ci has been restarted. ni LOCAL SYSTEM RESET Alarm The local Multiserver unit has been reset. Diagnostic The RD signal is being internally looped to the TD signal and transmitted onto the VF line.
PAGE 231
Appendix D: Messages Screen Display Messages Message Message Type Explanation NO ASYNC CHANNELS WITHIN RANGE Info A port or ports in the range selected is not configured for async. NODE-CHANNEL NOT AVAILABLE ENTER CARRIAGE RETURN TO CONTINUE Info A link port number was entered when a sync, async, or voice/fax channel number was required. NODE ID ALREADY IN USE Info You are trying to configure a node ID that has already been assigned in the network.
PAGE 232
Multiserver 5000 Screen Display Messages Message Message Type Explanation OUTPUT DATA TEST COMPLETE Diagnostic An async channel output test is complete. PRESS BREAK TO TERMINATE TEST Diagnostic To terminate a channel loopback or channel output test, press the key. QUEUE n/c cl Event Port c of node n has been placed in a first-come, first-serve queue for the next available port in the class. ni RECEIVER BUSY LINK ci Event The local receiver detected a busy signal.
PAGE 233
Appendix D: Messages Screen Display Messages Message Message Type Explanation Info You have changed the sync protocol and did not perform a reset. It is necessary to reset the node before proceeding. ni RING DETECTED LINK # ci Event The number dialed (TX or RX, primary or secondary) is ringing. This message is displayed by the call answering modem. ni RX CONNECTION MADE LINK # ci Event A successful call was placed over the dial lines from the modem’s RX dial-line connection.
PAGE 234
Multiserver 5000 Screen Display Messages Message Message Type Explanation ni TRANSMITTER RING DETECT LINK ci Event A call is coming in on the transmitter side. ni TX CONNECTION MADE LINK # ci Event A successful call was placed over the dial-lines from the modem’s TX dial line connection. This message is displayed by the call-originating modem. Dialog • Node, class, module location, or port is unknown in the network. • Password for the class may be incorrect.
PAGE 235
Appendix D: Messages Screen Display Messages Message Message Type Explanation VOICE CHANNEL [n/c] TEST CLEARED Event Voice/fax port c on node n has cleared (stopped) the current diagnostic test. Dialog Sent whenever the port is placed in a queue (after requesting a class which is busy). This message will appear whenever a printable character is typed or pressed; it indicates your place (n) in the queue.
PAGE 236
Multiserver 5000 LCD Messages MESSAGE TYPE: Alarm Vital to the system’s operation; may cause an interruption to that operation. Event Occurs in the regular operation of the system; most likely will not affect the system’s operation. Info Informational. KEY: cl = Class name or MATRIX if matrix switching is used. n/c = Node ID (n)/channel number (c). In some cases the channel number will display CMD = Command Facility. ni = Node ID. nn = A variable amount. ml = Module location letter [B-E].
PAGE 237
Appendix D: Messages LCD Messages Message Message Type ARE YOU SURE? Info A reset is requested. If the answer is yes, press the EXEcute key to proceed with the reset. If the answer is no, press ANY OTHER KEY except the EXEcute key to terminate without a reset. ARE YOU SURE? EXE FORCES A RESET Info You have attempted to reconfigure a node number and ID. This invokes a reset and this message. Press EXE to accept the new configuration and invoke the reset. Press any other key to abort.
PAGE 238
Multiserver 5000 LCD Messages Message Message Type Explanation INTEGRAL DEVICE NOT YET DEFINED Info You have attempted to select an Integral Device Menu in which the device has been detected by the software, but is not yet identified. Example: A cold start occurs and the user attempts to access the ISU menu tree under diagnostics within the first ten seconds after the reset. Usually a second attempt will succeed.
PAGE 239
Appendix D: Messages LCD Messages Message Message Type Explanation LOCAL LINK RESET ci Event or Alarm Local link ci has been reset. NEW DATE: nn/nn Event or Alarm Appears at the beginning of each new day and when the date is reconfigured. NO ACTION TAKEN.
PAGE 240
Multiserver 5000 LCD Messages Message TERMINATED VOICE CHANNEL n/c IN SERVICE WARNING: RESET OCCURS. EXE TO EXECUTE 238 Message Type Explanation Info A diagnostic test has been stopped (terminated). Event or Alarm Termination of a busyout condition has occurred on the specified voice/fax channel. Info You have requested a menu option that involves a warm reset. This occurs in some channel loopback and integral diagnostic selections. Press EXEcute to continue, any other key to abort.
PAGE 241
Appendix E: Indicators Appendix E: Indicators AT BO A6 A5 A4 A3 A2 A1 Figure E-1. CCM Indicator Positions. Table E-1. CCM Indicators.
PAGE 242
Multiserver 5000 Table E-2.
PAGE 243
Appendix E: Indicators 6-CHANNEL CEM 6 5 4 3 2 1 12-CHANNEL CEM 12 11 10 9 8 7 6 5 4 3 2 1 Figure E-2. CEM Indicator Positions. Table E-3. CEM Indicators CCM LED Indicator Indicator Definition Off Flashing On n1 through n12 Channel number No data activity Data activity Data activity n = module location B through D (a CEM may not be placed in module location E) NOTE: On a force-connected sync port using either Fast Packet or TDM protocol, the indicator will remain on continuously.
PAGE 244
Multiserver 5000 CHANNEL 2 CHANNEL 1 OK LO RO LS RS TM OK LO RO LS RS TM Figure E-3. Voice/Fax Module Indicator Positions. Table E-4.
PAGE 245
Appendix E: Indicators CHANNEL 2 OK LO RO LS CHANNEL 1 RS TM OK LO RO LS RS TM +1 dB + -4 dBm THROUGH +1 dBm -15 dBm THROUGH -5 dBm -25 dBm THROUGH -16 dBm < -25 dBm LEGEND: = ON = OFF = GREEN LIGHT NORMAL = 2 LIGHTS ON. IF CONVERSATION IS GOING ON, THIRD LIGHT IS FLICKERING. Figure E-4. Voice/Fax Channel bar graphs for the Input Level Display Mode.
PAGE 246
Multiserver 5000 LL RT SI RD TD Figure E-5. CSU/DSU Module Indicator Positions. Table E-5.
PAGE 247
Appendix F: Device Applications Appendix F: Device Applications Extended WANG Support Feature (WANGX) The extended WANG support feature (WANGX) provides special buffer control, flow control, and code levels for WANG 2200 computer systems support. These systems include 2200 UP, 2200 MUP, and 2200 LVP all using the 2236 MXD terminal processor and the 2236 DE interactive terminal as a standalone device or with any WANG printer slaved to it.
PAGE 248
Multiserver 5000 Table F-1. Spool Mode User Terminal Configuration Multiserver 5000 Configuration Type of Terminal Term Type HP Channel Flow Control HP26XX CRTs 10 Enabled X-ON/X-OFF X-ON/X-OFF Non-HP 4 (TTY) Disabled X-ON/X-OFF X-ON/X-OFF n/a 19 Disabled None None HP2631 and HP2635 Printers • HP port should be enabled when Term Type 10 is configured by the CPU or the terminal user.
PAGE 249
Appendix G: Rackmount Installation Appendix G: Rackmount Installation The MS1 Rackmount Kit consists of the following items: Here is how to install your Multiserver unit in a 19-inch rack using the MS1 Rackmount Kit: 1. Install the clip nuts on the rack. Place the tray in the rack. • One rackmount tray • Four screws 2. Secure both sides of the tray to the rack, using the screws and the washers (see Figure G-1). • Four washers—nylon filler • Four washers—nickel finish 3.
PAGE 250
Multiserver 5000 EXE VER ISER 5000 MULT Figure G-2. The Multiserver fully installed in a 19-inch rack with the Rackmount Kit.
PAGE 251
APPENDIX H: Additional Information Appendix H: Additional Infomation UPGRADE INFORMATION IMPORTANT INFORMATION from Phase 2.5 to Phase 3.0 Parity Conversion When upgrading from a Phase 2.5 to a Phase 3.0 FEATUREPAK_ cartridge, a cold start is not required. The configuration remains intact. With the async channel parity conversion feature, you must insure that you have each async channel configured correctly for the attached device. Previously, it was transparent to these settings.
PAGE 252
Multiserver 5000 DSR Control Dual Link Load Balancing When configuring sync channels, note that the Forced On option of the DSR Control Menu forces DSR on (high) all the time rather than following the local DTR. In a point-to-point application, Marathon 5K units can be config- ured with dual links. Load Balancing allows data to be assigned to a specific link on a per packet basis dependent on the load of each link.
PAGE 253
APPENDIX H: Additional Information Network Management System (NETMan) Async Channel Parity Conversion MICOM’s NETMan is a software package for PCs that manages Marathon networks. This product comes in two versions: NETM- an I (manages up to ten nodes) and NETMan III (manages more than ten nodes and up to 254 networks). A node, in this case, is a NETMan-managed Marathon unit or a MICOM multiplexer. With NETMan, you can monitor, configure, diagnose, and gather statistics for your Marathon networks.
PAGE 254
Multiserver 5000 Glossary ABR, autobaud rate detection — A process by which a receiving device determines the data rate, code level, and stop bits of incoming data by examining the first character received (usually a preselected sign-on character). ABR allows a receiving device to accept data from a variety of transmitting devices operating at different data rates, which means that the receiver does not need to be configured for each specific data rate in advance.
PAGE 255
Glossary one bit, as in quadrature amplitude modulation, the baud rate is smaller than bps. BCC, block check character — A character added to the end of a transmission block for the purpose of error detection. BERT — Acronym for Bit Error Rate Tester. bit — Contraction of binary digit. This is the smallest unit of information and the basic unit in digital data communications. A bit can have a value of zero or one (mark or space in datacommunications terminology).
PAGE 256
Multiserver 5000 channel — A path for electrical transmission between two or more points without common carrier-provided terminal equipment such as a local connection to DTE. Also called circuit, line, data link, or path. It may be asynchronous, synchronous, or voice. channel number — The channel number describes a specific module location and connector and is used in the configuration process. For example, the CCM has six channel numbers: A1 through A6.
PAGE 257
Glossary CPU, central processing unit — The heart (main processor) of a computer system, or the computer system itself. , carriage return — A user-entered ASCII or EBCDIC control character used to position the print mechanism of a printer, or the cursor on a terminal display, at the left margin. CRC, cyclic redundancy check — An errordetection scheme in which the block-check character is the remainder after dividing all the serialized bits in a transmission block by a predetermined binary number.
PAGE 258
Multiserver 5000 DIT, direct in termination — A service offered by a PBX which allows incoming calls to the PBX to be routed directly to a selected telephone or group of telephones without operator intervention. Billing does not start until the telephone answers. DLC, data link control — A communications protocol that sets up, controls, checks, and terminates information transfer between two stations on a data link. domestic models, and 3 types (Types I, II, and V) in international models.
PAGE 259
Glossary Multiserver network. On incoming calls, the fax signals are routed automatically from either the PSTN or the Multiserver network to the fax machine. On outgoing calls, the desired destination network for the fax machine is selected by the user. FCC — A government board that has the power to regulate all U.S.A. interstate communications systems as well as all international communications systems that originate or terminate in the U.S.A. FDX — See full-duplex.
PAGE 260
Multiserver 5000 KTS, key telephone system — In industry usage, a telephone system in which the telephones have multiple pushbuttons to allow users to select outgoing/incoming calls directly, without dialing an access number such as 9. Generally, a key telephone system has limited internal telephone-to-telephone capacity. As related to the Multiserver’s voice/fax module, a strapping option for compatibility with KTS-type telephone-interface equipment.
PAGE 261
Glossary ms, millisecond — One-thousandth of a second. multiplexor — A device that divides a composite signal among several channels. mux — Short for multiplexor. mux link — A Multiserver-to-feeder-mux composite link. NAK, negative acknowledgment — A control character which indicates that the previous transmission block was received in error. node — Any Multiserver or feeder mux in the Multiserver network. Each node has a unique name (ID) and number.
PAGE 262
Multiserver 5000 point-to-point — A communications circuit or transmission path connecting two points. In the Multiserver unit that connection can be forceconnected (dedicated point-to-point) or switched (switched point-to-point). port — A physical connector on the back of the Multiserver unit. It can be configured as a link, or as a user channel. Also, an interface capable of attaching to a device for communications with another device.
PAGE 263
Glossary RS-422 — An EIA-recommended standard for cable lengths that extended the RS-232 50-foot limit. Although introduced as a companion standard with RS-449, RS-422 is most frequently implemented on unused pins of DB25 (RS-232) connectors. Electrically compatible with CCITT recommendation V.11. RS-423 — An EIA-recommended standard for cable lengths that extended the RS-232 50 foot limit. Although introduced as a companion standard with RS-422, RS-423 is not widely used.
PAGE 264
Multiserver 5000 strapping — A hard-wire method used in the Multiserver to configure a module. For example, on the voice/fax module strappable options include KTS, OPX, and E&M telephone interfaces, and Types I through V E&M interfaces. Also strappable are the input impedance options (600, and U.K./COMP) in the international voice/fax modules. STX, start of text — A control character used to indicate the beginning of a message.
PAGE 265
Glossary VF, voice frequency — Any frequency within that part of the audio-frequency range essential for the transmission of speech of commercial quality (300-3000 Hz). This is the frequency range used over telephone lines. voice compression — A method of minimizing bandwidth by reducing the number of bits required to transmit voice. warm start — A system reset that maintains the current configuration. A Multiserver warm start may be performed in the Command Facility or at the front of the unit.
PAGE 266
Multiserver 5000 LCD/Keyboard Menu Flow Chart Banner Message Section 13.2 © 1994 Black Box Corporation Review System Message Log Menu Functions (password) Section 13.3 Section 13.4 System Administration Diagnostics Configuration Section 13.5 Section 13.6 Section 13.
PAGE 267
Command Mode Async Channel Loopback Menu Flow Diagram Local Channel Configuration Command Facility Main Menu © 1994 Black Box Corporation Exit* Note: * Option only (no menu or display) Local Echo* Remote Echo* Local Fox* Data Rate Remote Fox* Code Level Parity Stop Bits View Configuration Async Channels Sync Channels Integral Device Channel Features Extended Features Switching Parameters Channel Status Interface Status Queue Status Channel Characteristics Node Status Voice/Fax Cha