297-8991-910 DMS-100 Family Ethernet Interface Unit User Guide TELECOM12 Standard 03.
DMS-100 Family Ethernet Interface Unit User Guide Document number: 297-8991-910 Product release: TELECOM12 Document release: Standard 03.01 Date: August 1999 © 1998 Northern Telecom All rights reserved Printed in the United States of America NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern Telecom.
iv 297-8991-910 Standard 03.
v Publication history August 1999 TELECOM12 Standard 03.01 Updated Chapter 2 and Appendix C in response to Feature 59010371, FTP Extended Functionality. May 1999 TELECOM09 Standard 02.02 Implemented design comments. March 1999 TL09 Standard 02.01 Updated table IPNETWRK with correct datafill. Implemented design review comments. TL08 Standard 02.01 References to file transport access manager (FTAM) deleted. TL07 February 1998 TL07 Standard 01.01 First standard release of this document.
vi Publication history 297-8991-910 Standard 03.
vii Contents About this document xv When to use this document xv How to check the version and issue of this document xv References in this document xv Internet request for comment documents xvi What precautionary messages mean xvii How commands, parameters, and responses are represented Input prompt (>) xviii Commands and fixed parameters xix Variables xix Responses xix Chapter 1: Introduction to the EIU xviii 21 Overview of the EIU 22 System architecture 23 DMS-bus interface and expansion 24 Inter-
viii Contents Operational measurements Chapter 2: 43 EIU messaging protocols 45 Software architecture 46 Supported protocols 49 Addressing 54 Protocol engineering 61 IP throttling 61 TCP connection management 61 FTP session control 63 Protocol buffer engineering 63 IP throttling 65 IP throttling for LPP 65 IP throttling for SSLPP 66 Chapter 3: EIU datafill Interdependency and auto-configuration 68 Table LIUINV 68 Datafill sequence and implications 69 Table LIUINV datafill 69 EIU MAC addresses 72 IP
Contents ix Datafill 95 Sample datafill for table ENTYPES 96 Table EXNDINV 96 Datafill sequence and implications 97 Datafill 98 Sample datafill for table EXNDINV 102 Chapter 4: EIU maintenance 103 EIU MAP level 104 Manual busy state 104 In-service state 104 EIU diagnostics 104 Out-of-service diagnostics 104 In-service diagnostics 105 In-service leaky bucket audit 105 EIU overload control 106 EIU sparing requirements 107 Automated system maintenance 108 Manual system maintenance 109 Logs relevant to EIU
x Contents IP addresses 150 Address masks 157 Network numbering example 158 Firewalls and network security 159 Variable-width subnetworks 160 Protocols related to Internet Protocol 160 Internet Protocol 160 Internet control message protocol 161 Transmission control protocol 161 User datagram protocol 161 Address resolution protocol 161 Reverse ARP 162 Proxy ARP 162 Inverse ARP 162 Bootstrap Protocol 162 File transfer protocol 163 Open shortest path first 163 Routing information protocol 163 Telnet 163 Appe
xi List of figures Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Overall architecture of enhanced SuperNode system 24 Ethernet interface data flow 26 EIU mapping to lower levels of the OSI communications model Link interface shelf, wit
xii Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44 Figure 45 Figure 46 Figure 47 Subnet mask: class C 156 IP addressing: class D 157 IP addressing: class E 157 Address mask example 158 Simple network numbering 159 Host configuration 166 Router configurations 167 Host and router configuration 168 Interface configuration part 1 169 Interface Configuration part 2 170 LPP architecture 181 SSLPP architecture 183 SNSE-LIS architecture 184 EIU MAC add
xiii List of tables Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 DMS-Core feature packages 38 DMS-bus port engineering requirements for peripherals 41 IP routing table 60 IP route list table 60 TCP connection limits by SuperNode subsystem 62 UDP connection limits by
xiv Table 34 Table 35 Table 36 Table 37 FTP operations reference: workstation to DMS FTP operations reference: DMS to workstation IP address classes 150 NIC IP address request form 172 297-8991-910 Standard 03.
xv About this document This document is a source of information for the Ethernet interface unit (EIU) product. The document provides the following information: • hardware description • protocol descriptions • datafill requirements • maintenance • background information supporting the main chapters When to use this document Use this document for understanding the installation of the EIU, and for operating and maintaining the EIU.
xvi • Commands Reference Manual, 297-1001-822 • DMS SuperNode DataSPAN Frame Relay Service Maintenance Guide, 297-5111-501 • DMS SuperNode SCP II Maintenance Guide, 297-5131-541 • Link Interface Unit (LIU7) Memory Calculation, System Engineering Bulletin SEB 92-01-001 • Link Interface Unit (LIU7) Memory Calculation for an End Office, System Engineering Bulletin SEB 92-03-004 • Link Interface Unit (LIU7) Memory Calculation for an Integrated Node, System Engineering Bulletin SEB 92-03-005 • LPP/
xvii • Clarifications and Extensions for the Bootstrap Protocol, RFC1542 • File Transfer Protocol, RFC959 • Internet Control Message Protocol, RCF792 • Internet Protocol, RFC791 • OSPF Version 2, RFC1583 • Reverse Address Resolution Protocol, RFC903 • Routing Information Protocol, RFC1058 • Telnet Protocol Specifications, RFC495 • Transmission Control Protocol, RFC793 • User Datagram Protocol, RFC768 • Using ARP to Implement Transparent Subnet Gateways, RFC1027 What precautionary mess
xviii CAUTION Possibility of equipment damage CAUTION Damage to the backplane connector pins Align the card before seating it, to avoid bending the backplane connector pins. Use light thumb pressure to align the card with the connectors.
xix Commands and fixed parameters Commands and fixed parameters that are entered at a MAP terminal are shown in uppercase letters: >BSY CTRL ctrl_no Variables Variables are shown in lowercase letters: >BSY CTRL ctrl_no The letters or numbers that the variable represents must be entered. Each variable is explained in a list that follows the command string. Responses Responses correspond to the MAP display and are shown in a different typeface: FP 3 Busy CTRL 0: Command request has been submitted.
xx 297-8991-910 Standard 03.
Chapter 1: Introduction to the EIU This chapter describes the Ethernet interface unit (EIU). CAUTION Possible loss of network security Using the EIU and a telnet or file transfer protocol (FTP) session to establish a maintenance and administration position (MAP) session can introduce a security risk to both the DMS node and its subtending network.
Chapter 1: Introduction to the EIU • EIU provisioning requirements • billing • service orders • user interface characteristics • logs, alarms, and operational measurements (OM) Overview of the EIU The EIU is an application-specific unit (ASU) that supports Ethernet connectivity on the DMS-100 switch. You can configure the EIU as either an IP router or an OSI router. The EIU also supports host services.
Chapter 1: Introduction to the EIU 23 • Cellular digital packet data (CDPD). The CDPD service transports datagrams between the mobile and private/public data networks. • Programmable service node (PSN). PSN is a flexible platform that lets operating companies rapidly deploy advanced services into their network. Deployment is achieved through a service control unit (SCU). The SCU is an external computing platform that controls the call processing on the switch using a high-speed data link.
Chapter 1: Introduction to the EIU Figure 1 Overall architecture of enhanced SuperNode system SLM 9-track tape DMS-core Network IOC DMS-bus SOS SOS UNIX SOS FP (flexible file system) AP (provisionable computing) AP (provisionable computing) EIU Ethernet Communications server (flexible data communications interface) Workstation X.25 DMS-bus interface and expansion Two methods are used to interface processing engines to the DMS-bus.
Chapter 1: Introduction to the EIU 25 second-level message switches are referred to as local message switches (LMS). The frame transport bus (F-bus) is a 32-Mbit/s messaging bus that resembles the MS in its protocol. The use of a narrower data path allows access to two buses through a single backplane. This feature lets a single processor card connect to both planes of the LMS and to survive faults on one plane.
Chapter 1: Introduction to the EIU Figure 2 Ethernet interface data flow DMS-bus Messaging path User AP (protocol processing, for example, terminal drivers) Data communications processor (transport interface) Ethernet LAN Workstations Communications server Terminals Data links Given the cost of the SuperNode cabinet infrastructure, providing the standard hard connection interfaces in this mechanical environment is not possible.
Chapter 1: Introduction to the EIU 27 The Ethernet interface takes advantage of commercially supported peripherals and functions. These interface devices are selected and qualified for applications in the DMS-100 switch, with particular attention to hardware compliance, maintainability, and the protocol set provided.
Chapter 1: Introduction to the EIU Figure 3 EIU mapping to lower levels of the OSI communications model OSI reference model layers EIU partitioning Logical link control EIU software Data link Layer Media access control Ethernet interface hardware Physical signaling Attachment unit interface Physical Layer Attachment unit interface AUI PB 15-conductor connectorized cable Media access unit External equipment Transmission medium RG-58 coaxial cable UTP PB 4-wire twisted pair, LAN hub Hardware d
Chapter 1: Introduction to the EIU 29 RAM. The NTEX22CA provides 32 Mbyte of RAM and higher throughput performance. NTEX22 also contains a peripheral bus (P-bus) to F-bus interface. The Pbus to F-bus interface connects the processor bus with the frame bus, which in turn is connected to the local message switch (LMS) through the rate adaptor. The IPF card is a common processor card used by almost all ASUs and runs the Support Operating System (SOS).
Chapter 1: Introduction to the EIU Figure 5 SSLPP, with 2-slot EIU locations Top view of SSLPP shelf 2-slot ASU Rear paddle boards NT9X85 Front cards Ethernet AUI PB NT9X84 2-slot EIU NTEX22 Ethernet interface card Integrated processor and F-bus card Figure 6 shows the placement of an LPP provisioned with an EIU on a DMS SuperNode switch.
Chapter 1: Introduction to the EIU 31 Figure 7 DMS SuperNode FLIS with an EIU F-bus 0 MS 0 DS512 links EIU Bus plane 0 EIU MS 1 Ethernet Bus plane1 EIU F-bus 1 Ethernet interface card (NT9X84) The EIC is based on commercial Ethernet interface chips. It supports one Ethernet communications link and processes all of the level 1 and part of the level 2 protocols for the Ethernet in hardware.
Chapter 1: Introduction to the EIU Figure 8 Ethernet interface architecture P-bus LPP NTEX22 CPU/IPF Ethernet Ethernet memory controller Multiport buffer memory Ethernet controller MAU Ethernet coaxial cable Ethernet physical interfaces The physical interface to the Ethernet system is defined by the paddle board located behind the EIC. The interfaces available are described in the following sections.
Chapter 1: Introduction to the EIU 33 For a 10BaseT twisted-pair LAN, the AUI connection is usually on one side with an RJ-11 telephone jack on the other. Typically, standard office four-wire circuits are used to connect the MAU to the hub. The hub is an electronic replacement for the multiple access properties of the coaxial cable. It generates the broadcast function for each message received. It is usually an AC-powered unit mounted in a 19-in rack.
Chapter 1: Introduction to the EIU interface shelf (SNSE LIS). Nortel has tested the EIU for installation, operation, administration, and maintenance on each of these platforms. EIU hardware capabilities and limitations The following points describe EIU-specific limitations: • An Ethernet message is 1518 bytes long, including 128 transmit and 128 receive buffers. • The EIP (NT9X85AA) implements the unshielded twisted-pair AUI interface, which provides the physical link to the LAN.
Chapter 1: Introduction to the EIU 35 — programs were not aware that a period of time had elapsed — The router stopped routing packets. The EIU remained fully functional throughout the broadcast storm test. Although traffic from the EIU stopped, this stoppage was due to all other components on the LAN being nonfunctional and there was nothing left for the EIU to communicate with.
Chapter 1: Introduction to the EIU System-wide limitations The EIU is collocated in an LPP shelf with other ASUs such as the link interface unit (LIU7) and frame relay interface unit (FRIU). The exact configuration of ASU-type units depends on the applications. The LPP is connected to the DMS-bus through eight DS30 links in a load-sharing arrangement. Each DS30 has a transfer capacity of approximately 256 Kbyte/s.
Chapter 1: Introduction to the EIU 37 The Ethernet address in the LIUINV table has the format of the Nortel SuperNode family range of addresses: X000075Fxxxxx, where X is hexadecimal notation and x is a variable. For more information on MAC addresses, refer to “Appendix I: Obtaining a MAC address”. Diagnostics for the EIU test only the Ethernet interface card (EIC) and the Ethernet interface paddle board (EIP). These diagnostics do not test the AUI cable.
Chapter 1: Introduction to the EIU TCP Each TCP connection has its own state machine. For the number of allowed connections, refer to Table 5, TCP connection limits by Supernode subsystem in this document. There are also SOS limitations in that applications that require hundreds or thousands of connections are not supported. Internet Protocol and Internet Control Message Protocol When an EIU goes ManB or SysB, any qualifying EIU that is available takes over.
Chapter 1: Introduction to the EIU 39 Table 1 DMS-Core feature packages Package Title Description NTXF19AA TCP/IP This package is the protocol software from the transport layer down to the link layer. NTXF19AA uses NTXF05AA. NTXS11AA FTP This package is the standard FTP client and server software. NTXS11AA uses NTXF19AA. NTX70AA Telnet/RMAP This package is the standard telnet server for remote MAP (RMAP) access.
Chapter 1: Introduction to the EIU is in 21R), the cards in the MS at the other end of the link must also be provisioned in slot 21. This example is shown in figure 9.
Chapter 1: Introduction to the EIU 41 The information in table 2 defines the port requirements for EIU installation. Table 2 DMS-bus port engineering requirements for peripherals Peripheral Message Switch links per plane LPP (DS-30) 4 Comments Port Card NT9X17AA Paddle Board NT9X23BA 1 LPP requires 1 MS port card EIU provisioning Provisioning of EIUs is application dependent. The number of EIUs required and their configuration is determined by a combination of product and software criteria.
Chapter 1: Introduction to the EIU — the EIU state • During normal operation, the default EIU routes all messages to the CM.
Chapter 1: Introduction to the EIU 43 Logs, alarms, and OMs In general, the subsystems that generate logs, alarms, and OMs do not have significant changes apart from the standard DMS-100 reporting sub-systems. CAUTION Possible loss of information If a telnet session drops, logs and OMs may be lost. Log reports All logs from the EIU conform to the DMS OAM infrastructure. Log messages are formatted in the DMS-core for display using the standard DMS log system.
Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.
Chapter 2: EIU messaging protocols This chapter describes the Ethernet interface unit (EIU) software architecture: • SuperNode software architecture • protocol engineering • Internet Protocol (IP) throttling CAUTION Possible loss of network security Using the Ethernet interface unit (EIU) and a telnet or file transfer protocol (FTP) session to establish a maintenance and administration position (MAP) session can introduce a security risk to both the DMS node and its subtending network.
Chapter 2: EIU messaging protocols Software architecture The protocol stack supported on the DMS-core includes the following: • bootstrap protocol (BOOTP) • file transfer protocol (FTP) • IP • telnet • transmission control protocol (TCP) • user datagram protocol (UDP) • simple network management protocol (SNMP) Software architecture also includes key protocols such as address resolution protocol (ARP), Internet control message protocol (ICMP) and routing information protocol (RIP)1.
Chapter 2: EIU messaging protocols 47 Figure 11 SuperNode TCP/ IP protocol stack Base_Tel-7 FTP SNMP TELNET BOOTP RIP TLI (transport layer interface) 20, 21 161, 162 23 TCP 67, 68 520 UDP ICMP IP ARP GNI (generic subnet interface) FTS ETHERNET The message flow between SuperNode nodes, and between SuperNode nodes and external Ethernet LAN, is shown in figure 12 in this section.
Chapter 2: EIU messaging protocols Figure 12 SuperNode TCP/IP message flow DMS-core File processor Applications Applications TCP/UDP TCP/UDP IP IP FTS FTS DMS-bus EIU Applications TCP/UDP IP FTS Ethernet Ethernet LAN Workstation Applications TCP IP Ethernet 297-8991-910 Standard 03.
Chapter 2: EIU messaging protocols 49 Supported protocols The EIU software is designed such that the EIU can be configured to run as one of the following: • Internet host: EIU is involved only in supporting applications such as Message Detail Recording for SS7 (MDR7) • Internet router: EIU is involved only in forwarding IP packets between SuperNode and Ethernet LAN • Internet host and Internet router: EIU forwards IP packets between SuperNode and Ethernet LAN, as well as supporting a local application
Chapter 2: EIU messaging protocols has an Ethernet card). Such nodes have to be on the same subnet as the CM to be configured through the BOOTP server on the CM, except if the maximum hops count accepted by the server is increased. File transfer protocol File transfer protocol has been implemented on all the SuperNode-based nodes including CM. FTP implementation contains client as well as server software. The client software lets the user application connect to a remote FTP server.
Chapter 2: EIU messaging protocols 51 detects and sets the record length. To manually set the record length, use the LRECL command. This command changes the record length locally at the client site and sends the command to the server. The command is applied locally, regardless of the server response (negative or positive).
Chapter 2: EIU messaging protocols Internet Protocol The IP control software supports the IP logic, which provides a connectionless datagram service between hosts. The IP software is designed such that the same modules provide IP host and IP router functionality.
Chapter 2: EIU messaging protocols 53 The MAPCI supports asynchronous output to both the scroll area and a “full screen” area. The input, however, is buffered in a line-by-line mode. This combination of features requires that the telnet client perform echoing of input characters. The telnet server translates MAP display updates into VT100 character strings and sends them to the telnet client at the remote end. Telnet clients must directly connect to the CM using the CM address.
Chapter 2: EIU messaging protocols Upon receiving RIP update from either another EIU or IP router on the LAN, the RIP software updates internal IP routing table. According to RFC1058, RIP response messages are transmitted every 30 s to Ethernet LAN. Addressing Within a single SuperNode switch, multiple hosts and multiple applications within a single host may simultaneously request TCP/IP services.
Chapter 2: EIU messaging protocols 55 “Appendix E: Understanding IP and IP addressing” for more information on Internet addressing. The IP address features and restrictions within the SuperNode switch are as follows: • The Class A, B, and C address schemes are supported. The Class D and E schemes are not supported. • The IP addresses for all SuperNode hosts are assigned through DMS table control (tables IPNETWRK, IPROUTER, and IPHOST). • The IP addresses for all SuperNode hosts are on a single subnet.
Chapter 2: EIU messaging protocols Figure 13 Typical configuration for LAN and SuperNode subnets CM SuperNode-side subnet EIU EIU LAN-side subnet For more information on IP addresses, refer to “Appendix H: IP network number requests” and “Appendix E: Understanding IP and IP addressing”. How to get IP addresses for SuperNode To ensure that the network portion of an IP address is unique, all IP addresses are assigned by a central authority, the Network Information Center (NIC).
Chapter 2: EIU messaging protocols 57 • the IP address class • the IP address subnet size based on number of subnets and the maximum number of hosts per subnet (also, consider future expansion of the network) • the IP addresses for HUBs and routers • the dynamic routing strategy (only RIP is supported on the EIU) • network security (if the network is connected to public network such as the Internet, security consideration is vital) Routing The IP is a network layer protocol using the ISO seven-la
Chapter 2: EIU messaging protocols • Upon failure of any one EIU IP router, the traffic is switched over to another available (in service) EIU IP router on the same LAN. • IP routing handles a mix of EIU IP routers and EIU hosts on the same LAN. • A simple load balancing scheme between multiple EIU IP routers is provided. The load balancing scheme sets specific EIUs as primary routers for the outgoing data.
Chapter 2: EIU messaging protocols 59 An example SuperNode Ethernet CM APX MS Ethernet LAN LIU7 APUX20 EIU201 EIU200 LIU7 APUX10 LMS EIU101 LMS EIU100 Figure 14 Ethernet LAN Router Router Workstation Ethernet LAN Workstation DMS-100 Family EIU User Guide TELECOM12
Chapter 2: EIU messaging protocols Routing tables The IP routing table structure is briefly explained here. The knowledge of IP routing tables is critical in understanding SuperNode IP routing issues. The SuperNode IP routing information is organized locally on all hosts in two separate tables. One table determines a routeset from a given destination IP address. An example of this table is shown in table 3.
Chapter 2: EIU messaging protocols 61 router is determined based on the simple load balancing rules and the status of the router. IP Screening Packets destined for the Supernode can be screened at the IP level. If the source of the packet is determined to be invalid, the packet is dropped by the EIU. For more information, refer to data schema table EXNDINV in this document. Protocol engineering This section provides information on engineering rules and data for each of the protocol layers.
Chapter 2: EIU messaging protocols Maximums are defined for the number of TCP connections allowed on a node, as shown in table 5. UDP connection maximums are shown in table 6 on page 62.
Chapter 2: EIU messaging protocols 63 cause TCP to drop the existing connections, which could cause a temporary outage of all TCP applications. FTP session control Similar to the concept of TCP numbers, FTP sessions (client and server) on each node are managed by the parameters FTPSVCON and FTPCLCON in table IPHOST. These parameters control the number of FTP server and client sessions allowed on a particular node.
Chapter 2: EIU messaging protocols • medium (1024 bytes) • large (1600 bytes) When the IP layer comes into service, the number of buffers allocated by default is 10 for the small buffer size and 5 each for the medium and large buffer sizes. These values are load and application dependent. When the TCP layer comes into service, it allocates its own pool of transmit buffers and adds buffers to the common pool of receive buffers. The common pool of buffers is used for receiving IP and TCP packets.
Chapter 2: EIU messaging protocols 65 Table 7 Buffer allocation per end point (continued) Protocol Buffer type Number of buffers Size (in bytes) ICBM common pool 10 128 Transmit (application must allocate the number of buffers and size) 0 0 (Sheet 2 of 2) IP throttling IP throttle engineering is required to control congestion in the DS30 links. LPPs, SSLPPs, and SNSE-LISs have different throttling requirements, as described in the following sections.
Chapter 2: EIU messaging protocols Table 8 IP throttling values for LPP (continued) Approved BCS BCS36 Approved CSP CSP02 CSP04/05 Approved S/W IP router application EIU Tx Rx CM EIU Tx Tx Rx CSP04 CSP04 TOPS IEC04 CM EIU Tx Tx Rx CM EIU Tx Tx CM Rx Tx Note 1: Values for DS30 in kbyte/s Note 2: EIU = LMS node Note 3: CM = SuperNode (Sheet 2 of 2) IP throttling for SSLPP The SSLPP incorporates additional throttling control for TCP/IP traffic sent over SR256 between the MS an
Chapter 3: EIU datafill This chapter describes the datafill requirements for installing and maintaining Ethernet interface units (EIU) in an Ethernet network. There are seven data schema tables required to provision the EIU. The purpose of each table is summarized in table 10.
Chapter 3: EIU datafill The following sections describe these tables as they apply to EIU provisioning. For complete information on data schema, refer to DMS-100 Translations Guide, 297-8xxx-350. Interdependency and auto-configuration Tables IPROUTER and IPHOST are interdependent on each other, as well as on table IPNETWRK. Whenever a tuple in table IPROUTER is modified, the corresponding tuple, if any (with the same EIU), in table IPHOST is also modified and auto-configured.
Chapter 3: EIU datafill 69 Datafill sequence and implications The following tables must be datafilled before table LIUINV: • PMLOADS • LIMINV • CARRMTC • SUSHELF • LIMPTINV (LIM-based LIU) • MSCDINV (MS-based LIU) You must datafill the EIU in table LIUINV before datafilling it in table IPHOST. Table LIUINV datafill Table 11 lists the fields and value ranges used to datafill an EIU in table LIUINV.
Chapter 3: EIU datafill Table 11 Field descriptions for table LIUINV for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action LIUNO 0 to 511 Link interface unit number Enter the number assigned to the EIU. LOCATION The actual physical location of the EIU. This field identifies the shelf and slot number where the EIU is located LOCATION see subfields Location Enter the location of the EIU on the host link interface module.
Chapter 3: EIU datafill 71 Table 11 Field descriptions for table LIUINV for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action LIUSLOT 8 to 31 Link interface slot Enter the slot number, at the host LIM, on which the EIU resides. The EIU occupies two card slots. The left-most card represents the logical location of the card. All the shelves that are datafilled on a particular controller must be of the same type (two-slot shelves).
Chapter 3: EIU datafill Table 11 Field descriptions for table LIUINV for EIU datafill (continued) Field Subfield or refinement CARDINFO APPLPEC Entry Explanation and action see subfields Card information This field specifies the card data and consists of subfield APPLPEC. NT9X84AA Application product engineering code Enter the PEC of the application card. Card NT9X84AA is used with EIU applications. This field consists of subfields PBPED, HEARTBEAT, and MAC_ADDRESS.
Chapter 3: EIU datafill 73 MAC address is datafilled. The operating company obtains the MAC address from Nortel, and Nortel in turn controls the distribution of the addresses so that all addresses remain unique. The operating company must ensure that this address is datafilled correctly for each EIU. For details on MAC addresses, refer to “Appendix I: Obtaining a MAC address”. IP addresses By industry convention, IP addresses must also be unique.
Chapter 3: EIU datafill • routing tables and algorithms are added to the IP as part of its addressing function • the capability to datafill and distribute configurable information that is associated with the TCP/IP protocols using table control and the distributed data manager is added Datafill sequence and implications Before datafilling table IPNETWRK, the following prerequisites must be in place: • the EIU must be datafilled in LIUINV table • Nortel Networks recommends to place the default EIU
Chapter 3: EIU datafill 75 While table 12 provides all the information you need to datafill for EIUs, complete information on table IPNETWRK is in DMS-100 Translations Guide, 297-xxxx-350. Table 12 Field descriptions for table IPNETWRK for EIU datafill Field Subfield or refinement Entry Explanation and action refer to subfield Key reference. This field consists of subfield TAB_KEY. 0 to 15 Table key. Enter data in the network interfaces. You can enter a maximum of 16 entries.
Chapter 3: EIU datafill Table 12 Field descriptions for table IPNETWRK for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action PARM SCRNFLAG Parameter. If a screening flag is a requirement, enter SCRNGLAG. Enter refinement SCRNFLAG. EIU_INTERFACE To specify an EIU interface as the LAN interface for the CM, enter refinements for WORD_EIU and EIU_RNG. DFLT_GTWY_IP ADDR If a default gateway IP address for the network is a requirement, enter refinement GTWY_IPADDR.
Chapter 3: EIU datafill 77 Table 12 Field descriptions for table IPNETWRK for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action SCRNFLAG Y or N Screen flag. If the entry in subfield PARM is SCRNFLAG, datafill this refinement. To activate IP screening, enter Y. To deactivate IP screening, enter N. Refer to data schema table EXNDINV in this document for IP screening capability.
Chapter 3: EIU datafill Supplementary information The TRANSLATE command in the NETMAN tool can be used to convert an IP address into network parameters and vice versa.
Chapter 3: EIU datafill 79 Datafill sequence and implications The following tables must be datafilled before table IPROUTER: • PMLOADS • LIUINV • IPNETWRK Before entering data in table IPROUTER, Nortel Networks recommends to place the default EIU in the off-line state. Datafill Table 13 lists the fields and value ranges used to datafill an EIU in table IPROUTER.
Chapter 3: EIU datafill Table 13 Field descriptions for table IPROUTER for EIU datafill (continued) Field Subfield or refinement ETHARP Entry Explanation and action YES or NO Ethernet address resolution protocol Enter YES if the EIU is to engage in address resolution protocol (ARP) activity within the Ethernet subnet. Otherwise, enter NO. The default value for this field is YES.
Chapter 3: EIU datafill 81 Datafill sequence and implications The following tables must be datafilled before table IPHOST: • IPNETWRK • Inventory tables for nodes that are datafilled in field nodename in table IPHOST Before entering data into table IPROUTER, Nortel Networks recommends placing the corresponding EIUs referred to in the datafill in the OFFL state.. Note: In the assignment of IP addresses, the LAN side and the workstation need to be on different subnets from the DMS peripheral module (PM).
Chapter 3: EIU datafill Table 14 Field descriptions for table IPHOST for EIU datafill (continued) Field Subfield or refinement NODENAME Entry Explana tion and action AP, APU, CM , EIU, ELIU, FP,MS Node name Enter the node name: • AP (application processor) • APU (application processor UNIX) • CM (computing module) • EIU (Ethernet interface unit) • FP (file processor) • MS (message switch) Note: You can enter AP and FP to support the Supernode Unix (SNIX) versions of the nodes.
Chapter 3: EIU datafill 83 The datafill appears in the following table. Table 15 Field descriptions for conditional datafill for NODENAME = AP Field Subfield or refinement Entry Explanation and action SMNINDEX 0 to 99 File processor index Enter the FP index number. SNADDR table of 4 (0 to 255) Internet porotocol address SuperNode Enter the address of the SuperNode side.
Chapter 3: EIU datafill The datafill appears in the following table. Table 16 Field descriptions for conditional datafill for NODENAME = APU Field Subfield or refinement Entry Explanation and action APUINDEX 0 to 1 Application processor UNIX index Enter the APU index number. SOSADDR table of 4 (0 to 255) Support Operating Switch Enter the support operating switch address. UNIXADDR table of 4 (0 to 255) Internet protocol host identification for APU Enter the support operating switch.
Chapter 3: EIU datafill 85 The datafill appears in the following table. Table 17 Field descriptions for conditional data for NODENAME = CM Field Subfield or refinement Entry Explanation and action CMINDEX 0 to 1 Computing module index Enter the CM index number. TCPCONN 0 to 96 Transmission control protocol connections Enter the TCP connections number. FTPCLCON 0 to 48 File transfer protocol connections Enter the maximum number of FTP client sessions.
Chapter 3: EIU datafill The datafill appears in the following table. Table 18 Field descriptions for conditional datafill for NODENAME = EIU Field Subfield or refinement Entry Explanation and action EIUINDEX 0 to 750 Ethernet interface unit index Enter the EIU number. SNADDR table of 4 (0 to 255) Internet protocol address for node Enter the IP address of the SuperNode side of the node. LANADDR table of 4 (0 to 255) Second IP address for EIU host Enter the second IP address fo the EIU host.
Chapter 3: EIU datafill 87 The datafill appears in the following table. Table 19 Field descriptions for conditional datafill for NODENAME = ELIU Field Subfield or refinement Entry Explanation and action ELIUINDEX 0 to 750 Ethernet interface unit index Enter the ELIU number. SNADDR table of 4 (0 to 255) Internet protocol address for node Enter the IP address of the SuperNode side of the node.
Chapter 3: EIU datafill The datafill appears in the following table. Table 20 Field descriptions for conditional datafill for NODENAME = FP Field Subfield or refinement Entry Explanation and action SMNINDEX 0 to 99 File processor index Enter the file processor index number. SNADDR table of 4 (0 to 255) Internet Protocol address for node Enter the IP address of the SuperNode side of the node.
Chapter 3: EIU datafill 89 The datafill appears in the following table. Table 21 Field descriptions for conditional datafill for NODENAME = MS Field Subfield or refinement Entry Explanation and action MSINDEX 0 to 1 Message switch index Enter the MS index. SNADDR table of 4 (0 to 255) Internet Protocol address for node Enter the IP address of the SuperNode side of the node. TCPCONN 0 Transmission control protocol connections Enter the TCP connections number.
Chapter 3: EIU datafill • The first two fields for the tuple are numbers between 0 (zero) and 32 767 that represents the maximum IP transmit-and-receive rate in kbyte/s to and from the node that is datafilled as a key. • The IP throttling numbers default to zero (100% throttling) for all EIUs datafilled in table LIUINV. This means that if the throttling capacity numbers are not modified to numbers more than zero in this table, the EIU cannot communicate to nodes across DS30 links.
Chapter 3: EIU datafill 91 For more information on throttling, refer to“IP throttling” on page 61 and to the Provisioning Rules for LPP, SSLPP, and SNSE LIS, System Engineering Bulletin number 92-02-001, version 01.09. Datafill sequence and implications The following tables must be datafilled before table IPTHRON: • inventory tables for nodes that are datafilled in field SNNODE in table IPTHRON Datafill Table 22 on page 91 lists the fields and value ranges used to datafill an EIU in table IPHOST.
Chapter 3: EIU datafill Table 22 Field descriptions for table IPTHRON for EIU datafill (continued) Field Subfield or refinement OPTION SNNODE Entry Explanation and action see subfield Option This field consists of subfield SNNODE. AP, APU, CM, EIU, ELIU, FP, or MS SuperNode node Enter the name of the SuperNode node. The node must first be datafilled in its inventory table. For example, FP must be datafilled in table APINV. Up to eight nodes can be entered.
Chapter 3: EIU datafill 93 Table 22 Field descriptions for table IPTHRON for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action EIUINDEX 0 to 750 Ethernet interface unit index If the entry in field SNNODE is EIU, enter the EIU index. Go to refinement TXCAPCT. ELIUINDEX 0 to 750 Ethernet link interface unit index If the entry in field SNNODE is ELIU, enter the ELIU index. Go to refinement TXCAPCT.
Chapter 3: EIU datafill If there is a serious performance problem, typically on very slow networks, modification of this table may be considered to increase timeout values. Datafill sequence and implications There are no datafill sequence and implications. Datafill Table 23 lists the fields and value ranges used to datafill an EIU in table IPPROTO.
Chapter 3: EIU datafill 95 Table ENSITES Table ENSITES contains a complete list of all sites referenced in table EXNDINV. Datafill sequence and implications There are no datafill sequence and implications. Datafill Table 24 lists the fields and value ranges used to datafill an EIU in table ENSITES. While table 24 provides all the information you need to datafill for EIUs, complete information on table ENSITES is in DMS-100 Translations Guide, 297-xxxx-350.
Chapter 3: EIU datafill While table 25 provides all the information you need to datafill for EIUs, complete information on table ENTYPES is in DMS-100 Translations Guide, 297-xxxx-350. Table 25 Field descriptions for table ENTYPE for EIU datafill Field Subfield or refinement ENTYPE Entry alphanumeric (1 to 12 characters) Explanation and action External node type Enter the type of external node (for example, SUN or HP).
Chapter 3: EIU datafill 97 Table EXNDINV filters IP packets. Only packets with a specified source IP address can access DMS IP nodes. The SCRNFLG option in table IPNETWRK enables this functionality Figure 23 shows table EXNDINV filtering IP packets Figure 23 Table EXNDINV filters IP packets Base_Tel-6 47.105.150.1 CM EIU 1 47.208.8.2 47.105.150.2 Note: Packets for WS #1 are blocked while packets from TABLE IPNETWRK 0 47 105 150 1 WS #1 47.208.8.96 WS #2 47.208.8.
Chapter 3: EIU datafill Datafill Table 26 lists the fields and value ranges used to datafill an EIU in table EXNDINV. While table 26 provides all the information you need to datafill for EIUs, complete information on table EXNDINV is in DMS-100 Translations Guide, 297-xxxx-350.
Chapter 3: EIU datafill 99 Table 26 Field descriptions for table EXNDINV for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action IPADDRESS 0 to 255 (table of 4) Internet Protocol address If the entry in field ADDRTYPE is equal to ENIP, enter the IP address of the node. An IP address consists of 4 bytes, each with a value in the range 0 to 255. The IP address is usually expressed in the form 255.255.255.255.
Chapter 3: EIU datafill Table 26 Field descriptions for table EXNDINV for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action FLOOR 0 to 99 Floor number Enter the number of the floor on which the node is located. ROW A to Z or AA to ZZ (excluding I, O, II, and OO) Row Enter the row on the floor in which the node is located. POSITION 0 to 99 Bay position Enter the position of the bay in the row where the node is located.
Chapter 3: EIU datafill 101 Table 26 Field descriptions for table EXNDINV for EIU datafill (continued) Field Subfield or refinement EN0LKALM Entry Explanation and action CR MJ MN NA External node no-link alarm Enter the type of alarm to be raised if no links are available to the external node: • CR (critical alarm) • MJ (major alarm) • MN (minor alarm) • NA (no alarm) EN1LKALM CR MJ MN NA External node one-link alarm Enter the type of alarm to be raised if only one link is available to the
Chapter 3: EIU datafill Table 26 Field descriptions for table EXNDINV for EIU datafill (continued) Field Subfield or refinement Entry Explanation and action MAJSCPT 0 to 6 Major alarm scan point Enter the scan point associated with the major alarm for the node. MINSCPT 0 to 6 Minor alarm scan point Enter the scan point associated with the minor alarm for the node. (Sheet 5 of 5) Sample datafill for table EXNDINV Figure 24 shows sample datafill for table EXNDINV for an EIU.
Chapter 4: EIU maintenance This chapter provides information on Ethernet interface unit (EIU) maintenance. CAUTION Possible loss of network security Using the Ethernet interface unit (EIU) and a telnet or file transfer protocol (FTP) session to establish a maintenance and administration position (MAP) session can introduce a security risk to both the DMS node and its subtending network.
Chapter 4: EIU maintenance EIU MAP level EIU information is available on the maintenance and administration position command interface (MAPCI) display under the PM level. The command to access the EIU MAP display is as follows: >MAPCI;MTC;PM;POST EIU n|ALL where n is the EIU index The maintenance actions implemented for an EIU are similar to those required for any other application-specific unit (ASU) on the LPP.
Chapter 4: EIU maintenance 105 or the MAP display. The TST command in MAPCI also executes the same diagnostics when the EIU is ManB. In-service diagnostics The EIU changes its state to SysB state from InSv or IsTb if a serious hardware fault is detected by the in-service audit process. The in-service audits periodically run diagnostics on some critical EIU hardware components. The audits run every minute, each time checking one quarter of the hardware components.
Chapter 4: EIU maintenance Table 27 summarizes the preset bucket parameters for reported LAN faults.
Chapter 4: EIU maintenance 107 The EIU remained fully functional throughout the test. Although traffic from the EIU stopped, the stoppage was due to all other components on the LAN being non-functional and there was nothing left for the EIU to communicate with. These test also showed that maintenance personnel could remote login to the EIU, start a CI process, look at OMs, and finally remote logout.
Chapter 4: EIU maintenance A simple form of load balancing is used such that multiple end-hosts in the DMS switch are assigned an active EIU in a round-robin fashion. This requirement does not take into account the relative amounts of traffic to or from the end hosts. For more information on EIU redundancy and sparing, refer to “EIU sparing and redundancy” on page 39. Figure 25 shows the EIU redundant configuration.
Chapter 4: EIU maintenance 109 indicators drive “fault thresholds” that trigger maintenance actions when exceeded. • periodic functional audits to ensure that the hardware still functions • out-of-band resets that the DMS-100 switch initiates when detecting a severe problem. An out-of-band reset is a hardware reset that is propagated outside of the normal message processing and protocol paths. The EIU hardware diagnostics do not extend beyond the EIP (NT9X85).
Chapter 4: EIU maintenance For information and procedures, refer to Card Replacement Procedures, 297-xxxx-547. Logs relevant to EIU OA&M The following logs are relevant to EIU operations, administration, and maintenance: • TELN • ITN Note: For more information on these logs, refer to the DMS 100 Logs Reports Reference Manual, 297-xxxx-840.
Appendix A: EIU installation checklist This appendix provides a checklist of activities that the operating company follows to install Ethernet interface units (EIU) in a DMS-100 switch. CAUTION Possible loss of network security Using the Ethernet interface unit (EIU) and a telnet or file transfer protocol (FTP) session to establish a maintenance and administration position (MAP) session can introduce a security risk to both the DMS node and its subtending network.
Appendix A: EIU installation checklist Use the list in table 28 as a checklist to ensure that you meet all installation requirements for hardware, software, and datafill.
Appendix B: EIU troubleshooting This appendix provides information on tools that are commonly used in troubleshooting problems with the Ethernet interface unit (EIU). The appendix also provides a summary of common problems and possible causes.
Appendix B: EIU troubleshooting Tools Table 29 summarizes the tools available for troubleshooting the EIU.
Appendix B: EIU troubleshooting 115 Table 30 EIU troubleshooting checklist (continued) Problem Probable cause Cannot set up an FTP session between a SuperNode-based node and an external node 4, 8 Cannot ping between two SuperNode-based nodes 4, 5 Cannot set up an TCP connection between two SuperNodebased nodes 4, 5, 6 Cannot log in as the admin user 7, 8 Cannot setup an FTP session between two SuperNodebased nodes 4 Can ping EIU, but cannot ping the computing module (CM) 4 1 There are no EI
Appendix B: EIU troubleshooting 297-8991-910 Standard 03.
Appendix C: Using FTP This appendix provides information on using file transfer protocol (FTP) with the Ethernet interface unit (EIU). FTP is an internationally accepted protocol for exchanging files between computing devices. Exchanged files can be in many formats. Further, computing devices can be hosts with different and even incompatible file systems.
Appendix C: Using FTP What is FTP? FTP is a session-oriented tool, which means that you establish a session, through login, before the file exchange takes place. The login requires a secure userID and password. Create the secure userID and password via the FTP level or the FTP MIB using SNMP. FTP on the DMS-100 switch conforms to industry standards regulating FTP.
Appendix C: Using FTP 119 is the transfer type, txt for ASCII or bin for BINARY the logical record length is a number from 1 to 32767 This file format is shown in table 31. Table 31 Examples of filenames with record length in their extension File type Filename before transfer to the DMS Format DMS filename after transfer to the DMS XPM software file1.bin1024 binary, lrecl 1024 FILE1 XPM software file1e.txt54 ascii, lrecl 54 FILE1 MS software file1.
Appendix C: Using FTP If the file format is not recognized by the FTP application, the system aborts the file transfer and issues one of the following error messages. Example of an error message: ‘503 TYPE must be Binary.’ ‘503 TYPE must be ASCII.’ Volume listing The FTP application provides the ability to determine available volumes on the DMS-100 switch. Use the command ls / or to list the available active disk volumes on the DMS-100 switch.
Appendix C: Using FTP 121 Example: DMS>get source ‘/a/b/filename’ DMS>put ‘/a/b/filename’ destination • If you have a client session on the DMS-100 switch, destination and source file names on the local host can be in lowercase or uppercase. But since the DMS CI tries to convert every letter on the command line to uppercase, you must take care and place single quotes around path names that are in lowercase. Also, use single quotes when using a forward slash in a pathname or filename.
Appendix C: Using FTP Table 33 FTP commands on the DMS-100 switch (continued) Command Description DELUSERINFO delete user-related information DIR list the directory FTPCLOSE close the connection with the remote host FTPDEBUG set the debug messages on or off FTPOPEN establish a connection to the remote host FTPQUERY print the file attributes FTPQUIT close the connection GET get the file from the remote server HELP get information on commands LCD change the local working directory
Appendix C: Using FTP 123 If you need to find out the IP address of a SuperNode host, refer to the following tables: • table IPNETWRK for address of the CM • table IPHOST for addresses of all other SuperNode hosts Tutorial: basic FTP operations This section provides a set of procedures for using FTP on the DMS-100 switch to transfer files to and from the DMS-100 switch. Use these procedures as either reference or as a tutorial.
Appendix C: Using FTP where passwd is a valid user password for the userID that you are using You are placed in the default directory. Example of a MAP response: 230 User johnh logged in. 4 You have completed this procedure. Procedure 2 Determining your directory location Step Action 1 Establish an FTP session as described in procedure 1 in this appendix. 2 Request the current directory path by typing ftp> pwd and pressing the Enter key.
Appendix C: Using FTP 125 3 List the files names and their attributes in the directory by typing ftp> dir and pressing the Enter key. Example of a MAP response: total 57512 drwx-----2 paulg snopc drwx-----2 paulg snopc -rw-r--r-1 paulg gtest drwxr-xr-x 4 paulg snopc -rw-r----1 paulg snopc drwxr-x--2 paulg snopc drwxr-x--3 paulg snopc 226 Transfer complete. 4 512 Jan 26 512 Feb 2 397 Jan 4 512 Nov 30 557879 Feb 512 Jan 22 4608 Feb 1 08:05 News 07:55 PERSONAL 1995 .
Appendix C: Using FTP 2 You have completed this procedure. Tutorial: moving files This section provides a set of procedures to move files between a remote host and the DMS-100 switch which is the local host.
Appendix C: Using FTP 127 5 6 Determine the next step. If the file Do is not stored the current local directory step 6 is stored on the current local directory step 7 Change directory on the local host (DMS-100 switch) by typing ftp> lcd path_name and pressing the Enter key. where path_name is a valid directory path Example: ftp> lcd ‘/S00DTEMP’ Example of a MAP response FTP: Local directory changed. 7 8 Determine the next step.
Appendix C: Using FTP 9 Get an ASCII file from the remote host by typing ftp>get file_name1 and pressing the Enter key. where file_name1 is the name of the file on the remote directory Example: ftp> get ‘file1.dmo’ This example gets a file named file1.dmo from the remote host and renames it to FILE1 on the DMS-100 switch. Example of a MAP response: 226 Transfer complete. 35334bytes transferred in 0 hrs. 0 mins. 12 secs. 42 ms. (3282 Bps) Go to step 11.
Appendix C: Using FTP 129 12 You have completed this procedure. Procedure 6 Copying a binary file from the remote host Step Action 1 Establish an FTP session and determine your location as described in procedure 1 in this appendix. 2 Determine the next step 3 If the file Do is not on the current remote directory step 3 is on the current remote directory step 4 Change directory on the remote host by typing ftp> cd path_name and pressing the Enter key.
Appendix C: Using FTP where path_name is a valid directory path Example: ftp> lcd ‘/S00DTEMP’ 7 8 Determine the next step. If the filename Do has an extension that CANNOT have the record length automatically detected. Refer to the section “Automatic record length detection is this appendix”. step 8 has an extension that can have the record length automatically detected step 10 Set the record length of the file by typing ftp> lrecl rec_length and pressing the Enter key.
Appendix C: Using FTP 131 where file_name1 is the name of the file on the remote directory Example: ftp> get ‘file1.bin1020’ This example gets a file called file1.bin1020 from the remote host and renames it to FILE1 on the DMS-100 switch. 11 You have completed this procedure. Tutorial: advanced operations This section provides a set of procedures that demonstrate how to add FTP users on the DMS-100 switch.
Appendix C: Using FTP 1 Start the FTP tool without connecting to a host by typing ftp> ftp and pressing the Enter key. 2 Reserve a session by typing ftp> svreserve 1 and pressing the Enter key. Example: ftp> svreserve 1 Example of a MAP response: 1 SERVER SESSION RESERVED TOTAL NUMBER OF SERVER SESSIONS RESERVED -> 1 3 Add user information associated with the reserved sessions by typing ftp> adduserinfo user_id passwd default_dir privilege and pressing the Enter key.
Appendix C: Using FTP 133 where user_id is the userID Example: ftp>deluserinfo ‘johnh’ Example of a MAP response: DELETE USERINFO PASSED This userID can no longer FTP to this node and login using the userID and password of johnh johnh. 3 Unreserve a session by typing ftp> svunreserve 1 and pressing the Enter key. Example: ftp>svunreserve 1 Example of a MAP response: 0 SERVER SESSIONS STILL RESERVED. 4 You have completed this procedure.
Appendix C: Using FTP ftp> commandmask mkdir set Example of a MAP response: Command mask for the mkdir command has been set 4 Add user information associated with this command mask by typing ftp> adduserinfo user_id passwd default_dir privilege and pressing the Enter key.
Appendix C: Using FTP 135 Example: ftp>commandtimeout Default command timout value is 10 mins. 3 Set the default command timeout value to forever by typing ftp> commandtimeout value and pressing the Enter key. where value is a time value in minutes. A value of 0 means forever. Example: ftp>commandmask 0 Example of a MAP response: Default command timeout value has been changed to forever.
Appendix C: Using FTP Table 34 shows FTP operations for sessions started on a workstation for connection to a DMS-100 switch. In this scenario, the DMS-100 switch is the remote host and the workstation is the local host. Table 34 FTP operations reference: workstation to DMS Action Command sequence FTP login WS> ftp IP_address where IP_address is the address of the remote host. Enter a valid FTP userID and password to complete login.
Appendix C: Using FTP 137 Table 34 FTP operations reference: workstation to DMS Action Command sequence Get an ASCII file from the DMS WS> ascii WS> get file_name where file_name is the name of the file on the DMS that you want to get. If the file name is in lowercase, use single quotation marks around the name (including forward slashes).
Appendix C: Using FTP Table 34 FTP operations reference: workstation to DMS Action Command sequence Send an image file to the DMS WS> binary WS> site lrecl 1020 WS>put file_name.image FILE_NAME where file_name is the name of the file on the workstation and FILE_NAME is the target file name, in uppercase, on the DMS. Send an unIPLed load to the DMS WS> binary WS> site lrecl 512 WS> put file_name.
Appendix C: Using FTP 139 Table 35 FTP operations reference: DMS to workstation Action Command sequence Change the working directory on the workstation CM> cd ‘path_name’ where path_name is a valid path from the current working directory on the workstation Use single quotation marks only if the directory name is in lowercase.
Appendix C: Using FTP Table 35 FTP operations reference: DMS to workstation Action Command sequence Send an ASCII file to the workstation CM> ascii CM> put file_name where file_name is the name of the target file on the workstation. If the file name is in lowercase or contains forward slashes, use single quotation marks around the name. The above command sequence • sets the transfer type to ASCII • puts the file in the current directory of the workstation.
Appendix D: Using telnet This appendix provides procedures for establishing telnet sessions on the DMS-100 switch. CAUTION Possible loss of network security Using the Ethernet interface unit (EIU) and a telnet or file transfer protocol (FTP) session to establish a maintenance and administration position (MAP) session can introduce a security risk to both the DMS node and its subtending network.
Appendix D: Using telnet Telnet access to a switch CAUTION Possible loss of service To avoid reliability problems, establish telnet sessions on the DMS switch only with CSP05 software and above. If you encounter problems, contact your next level of support. Procedure 12 Telnetting into a switch for MAP session access (pre-CSP05) Step Action 1 Go to the CI level of the MAP display. 2 Open table IPHOST by typing >table IPHOST and pressing the Enter key.
Appendix D: Using telnet 143 Procedure 13 Telnetting into a switch for MAP session access (CSP05 and up) Step Action 1 Go to the CI level of the MAP display. 2 Open table IPNETWRK by typing >table IPNETWRK and pressing the Enter key. 3 Determine the IP address for the CM. 4 Close table IPNETWRK by typing >quit and pressing the Enter key. 5 Open table IPHOST by typing >table IPHOST and pressing the Enter key. 6 Determine that there are enough TCP connections for the CM.
Appendix D: Using telnet 297-8991-910 Standard 03.
Appendix E: Understanding IP and IP addressing This chapter is a primer on internetworking, Internet Protocol (IP), addressing, and IP-related protocols. For examples on IP addressing and configurations, refer to “Appendix F: EIU addressing examples”. What is internetworking? Internetworking began as a method of connecting stand-alone local area networks (LAN) to allow sharing of information between different parts of an enterprise (corporation, campus, and so on).
Appendix E: Understanding IP and IP addressing application that the user needed to access. Otherwise, the user required a separate line and terminal device for each application. As the number of communications duties grew (such as addressing, route selection, and error detection and correction), there came a point where the applications had to be uncoupled from the communications “network.” Specialized computers were created to take over the communications duties.
Appendix E: Understanding IP and IP addressing 147 The routed protocol of the architecture (usually the network-layer protocol) creates connectionless datagrams or packets. The address information contained in the datagram header enables each encountered router to make a routing decision for the datagram. The routed protocol of the TCP/IP architecture is the IP. The routing protocol distributes information on the availability or reachability of networks or subnetworks (also loosely referred to as wires).
Appendix E: Understanding IP and IP addressing Figure 26 Simple network map 133.25.30.8 Network 133.25.0.0 172.113.4.5 DMS-100 switch with EIUs Network 172.113.4.0 Main file server 172.113.4.2 Administrator station 133.25.2.1 The networks shown in figure 26 are established and only need to be joined to the EIUs. Consequently, the installers and administrators need only understand the network addresses for the ports and the routing protocol currently in use.
Appendix E: Understanding IP and IP addressing 149 Figure 27 Detailed network diagram DMS-100 switch with EIUs 138.109.3.1 138.109.2.1 138.109.4.1 138.109.2.2 To remote router 138.109.4.0 138.109.2.5 138.109.2.3 Network 138.109.2.0 Mask 255.255.255.0 138.109.2.11 Network 138.109.3.0 Mask 255.255.255.0 138.109.2.16 138.109.2.21 138.109.2.26 138.109.3.2 File server 138.109.3.3 Printer 138.109.3.4 138.109.2.31 138.109.2.
Appendix E: Understanding IP and IP addressing not recommended. If connection to public networks is needed later, all the addressing work must be repeated. IP addresses IP uses a 32-bit address, which consists of four sets of eight-bit numbers, normally expressed in decimal notation. For example, 147.234.011.101 is a valid IP address format. IP addresses can be divided into a network number and a host number, as shown in figure 28.
Appendix E: Understanding IP and IP addressing 151 Table 36 IP address classes Class Range Description C 192 to 223 This is used for smaller networks having fewer than 255 nodes, such as smaller colleges and businesses (for example, 195.10.107.0). Two additional address classes exist. Class D addresses support IP multicasting, which is used to transmit packets to multiple IP addresses. Class E addresses are reserved for Internet engineering task force experimental use.
Appendix E: Understanding IP and IP addressing Figure 29 IP addressing: class A Base_Tel-9 Class A addresses range from 1.X.X.X to 127.X.X.X (standard network mask is 255.0.0.0). Therefore, we can have 127-2 class A networks each with 16,777,216-2 hosts (if no subnets).
Appendix E: Understanding IP and IP addressing 153 Figure 30 Subnet mask: class A CLASS A subnet masks No. subnets No. hosts 2 6 14 30 62 126 254 510 1022 2046 4094 8190 16382 32766 65534 131070 262142 524286 1048574 2097150 4194302 4194302 2097150 1048574 524286 262142 131070 65534 32766 16382 8190 4094 2046 1022 510 254 126 62 30 14 6 2 netmask 255.192.0.0 255.224.0.0 255.240.0.0 255.248.0.0 255.252.0.0 255.254.0.0 255.255.0.0 255.255.128.0 255.255.192.0 255.255.224.0 255.255.240.0 255.255.248.
Appendix E: Understanding IP and IP addressing Figure 31 IP addressing: class B Base_Tel-11 Class B addresses range from 128.0.X.X to 191.255.X.X (standard network mask is 255.255.0.0), therefore, we can have 16384-2 class B networks each with 65536-2 hosts (if no subnets).
Appendix E: Understanding IP and IP addressing 155 Figure 32 Subnet mask: class B Base_Tel-12 CLASS B subnet masks No. subnets 2 6 14 30 62 126 254 510 1022 2046 4094 8190 16382 No. hosts netmask 16382 8190 4090 2046 1022 510 254 126 62 30 14 6 2 255.255.192.0 255.255.224.0 255.255.240.0 255.255.248.0 255.255.252.0 255.255.254.0 255.255.255.0 255.255.255.128 255.255.255.192 255.255.255.224 255.255.255.240 255.255.255.248 255.255.255.
Appendix E: Understanding IP and IP addressing Figure 33 IP addressing: class C Base_Tel-13 Class C addresses range from 192.0.0.X to 223.255.255.X (standard network mask is 255.255.255.0), therefore, we can have 16384-2 class C networks each with 65536-2 hosts (if no subnets).
Appendix E: Understanding IP and IP addressing 157 Figure 35 IP addressing: class D Base_Tel-15 Class D addresses are used to broadcast to all hosts on network. | 32 bits | 1110 multicast | 4 bit | 28 bits | Class D indicator Figure 36 IP addressing: class E Base_Tel-16 Class E addresses are experimental and are generally not used by the IP community.
Appendix E: Understanding IP and IP addressing departments. Each department expects to use fewer than 254 host addresses, so the entire third byte of the address is chosen for the subnetwork number. To reserve the third byte for the subnetwork number, they use subnetwork mask 255.255.255.0. Figure 37 on page 158 illustrates this point. Figure 37 Address mask example Network node (133.101.1.8) Class B network ID 133 Subnet ID Host ID 1 8 101 + Subnet mask (255.255.255.
Appendix E: Understanding IP and IP addressing 159 Figure 38 Simple network numbering Corporate router 22.0.0.0 21.0.0.0 20.0.0.0 23.1.0.0 Engineering router 23.2.0.0 23.3.0.0 23.4.0.0 The Corporate Networking group assigns a class A address to each of its departments. The three Ethernet networks on 20.0, 21.0, and 20.0.22.0 are sufficient to interconnect most of the organization. The Corporate Networking group reserves network 20.0.0.0 for its own use to interconnect the corporate computers.
Appendix E: Understanding IP and IP addressing representative to discuss state-of-the-art secure data communications equipment products. Variable-width subnetworks When subnetworks were first invented, they were intended to be used in a star topology, with the major router at the port of entry connected to all subnetworks. All subnetworks were supposed to have address ranges of the same size.
Appendix E: Understanding IP and IP addressing 161 Internet control message protocol The Internet control message protocol (ICMP) provides feedback from an IP router or gateway to a source host. ICMP messages are sent in several situations—for example, to report resource or routing problems or to report a shorter available route to a destination. The DMS-100 switch uses ICMP echoes and echo replies to verify the reachability of routers or end systems.
Appendix E: Understanding IP and IP addressing Included in the family of address resolution protocols are reverse address resolution protocol (RARP), proxy address resolution protocol (proxy ARP), and inverse address resolution protocol (InARP). ARP is defined in RFC826. Reverse ARP RARP is used to determine or assign a particular station IP address when only the station LAN MAC address is known. There are many reasons why an end system does not already have an IP address.
Appendix E: Understanding IP and IP addressing 163 • the IP address of a boot server host • the name of a file to be loaded into memory and executed • the local subnet mask • the local time offset • the addresses of default routers • the addresses of various Internet servers The EIU supports the BOOTP relay agent functionality described in RFC951 and RFC1542. File transfer protocol FTP provides a robust file transfer mechanism for data transfer between IP hosts.
Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.
Appendix F: EIU supported configurations This appendix provides examples of EIU supported configurations.
Appendix F: EIU supported configurations Figure 39 Host configuration Subnet 1 classA.networkidB.subnetX.hostZ Base_Tel-1 Subnet 2 classA.networkidB.subnetY.hostZ 47.105.150.1 47.105.144.3 CM 47.105.144.1 Host Can be another subnet or new network on this side of external router External router EIU 1 47.105.144.2 47.105.150.2 Notes: 1. Class and network are the same on both sides of EIU but subnets are different. 2: Subnet size must be the same for all subnets on a network.
Appendix F: EIU supported configurations 167 Figure 40 Router configurations Subnet 1 classA.networkidB.subnetX.hostZ 47.105.150.1 Base_Tel-8 Subnet 2 classA.networkidB.subnetY.hostZ 47.105.144.3 CM External router Host 47.105.150.2 EIU 1 47.105.144.1 47.105.144.2 Can be another subnet or new network on this side of external router EIU 2 47.105.150.3 47.105.144.4 Notes: 1. Class and network are the same on both sides of EIU but subnets are different.
Appendix F: EIU supported configurations Figure 41 Host and router configuration Subnet 1 classA.networkidB.subnetX.hostZ Base_Tel-2 Subnet 2 classA.networkidB.subnetY.hostZ 47.105.150.1 47.105.144.3 CM 47.105.144.1 External router Host 47.105.150.2 EIU 1 47.105.144.2 Can be another subnet or new network on this side of external router EIU 2 47.105.144.4 47.105.150.3 Notes: 1. Class and network are the same on both sides of EIU but subnets are different.
Appendix F: EIU supported configurations 169 Figure 42 Interface configuration part 1 Subnet 1 Base_Tel-3 Subnet 1 classA.networkidB.subnetX.hostZ classA.networkidB.subnetX.hostZ 47.105.150.1 47.105.150.2 CM 47.105.150.3 Host EIU 1 47.105.150.1 External router EIU 2 Can be another subnet or new network on this side of external router Note: The CM node can support up to 16 different IP addresses.
Appendix F: EIU supported configurations Figure 43 Interface Configuration part 2 Base_Tel-4 classA.networkidB.subnetX.hostZ Subnet 1 47.105.150.3 CM EIU 1 External router 47.105.150.1 Can be another subnet or new network on this side of external router classA.networkidB.subnetY.hostZ 47.105.160.1 47.105.160.2 Host 47.105.160.3 EIU 2 External router Can be another subnet or new network on this side of external router Subnet 2 Note: The CM node can support up to 16 different IP addresses.
Appendix G: IP network number requests This appendix provides information on obtaining an Internet Protocol (IP) address from the Network Information Center (NIC), including information on the type of addresses available and the form required to obtain the address. Overview NIC is the formal organization that regulates and assigns all IP addresses recognized on the Internet. NIC ensures that the network portion of an IP address is unique.
Appendix G: IP network number requests The network topology consists of the SuperNode and other third-party equipment, such as hubs and workstations. Some third-party routers may be required for distant LANs or for fault-tolerant network architecture.
Appendix G: IP network number requests 173 Table 37 NIC IP address request form IP address request form (continued) 1) If the network will be connected to the Internet, you must provide the name of the governmental sponsoring organization, and the name, title, mailing address, phone number, net mailbox, and NIC handle (if any) of the contact person (POC) at that organization who has authorized the network connection.
Appendix G: IP network number requests Table 37 NIC IP address request form IP address request form (continued) 3) Supply the short mnemonic name for the network (up to 12 characters). This is the name that will be used as an identifier in Internet name and address tables. 3a. Network name: 4) Identify the network geographic location and the responsible organization establishing the network. 4a. Postal address for main/headquarters network site: 4b.
Appendix G: IP network number requests 175 Table 37 NIC IP address request form IP address request form (continued) 7) Unless a strong and convincing reason is presented, the network (if it qualifies at all) will be assigned a class C network number. If a class C network number is not acceptable for your purposes state why. Note: If there are plans for more than a few local networks, and more than 100 hosts, you are strongly urged to consider subnetting. See RFC 950. 7a.
Appendix G: IP network number requests 297-8991-910 Standard 03.
Appendix H: ASU background information This appendix provides background information on application-specific units (ASU) and the SuperNode platforms that support these ASUs. Application-specific units and supported services The following ASUs are described in this section: • link interface unit (LIU7) • Ethernet interface unit (EIU) • frame relay interface unit (FRIU) • X.25/X.
Appendix H: ASU background information OSI router or support host services.
Appendix H: ASU background information 179 Network interface unit The NIU provides direct network connectivity for the link peripheral processor (LPP), the single-shelf LPP (SSLPP), or the SuperNode SE link interface shelf (SNSE LIS). The NIU gives some ASUs and services access to DS1 or PCM30 trunking without using channel banks or multiplexer equipment. Prior to the availability of the NIU, physical connections were limited to DS0 or V.35 located on paddle boards of the LIU7 ASU.
Appendix H: ASU background information • CDPD XLIU terminates various protocols, such as LAPB and MDLP. XLIUs also store accounting information for data services. • CDPD NIU stores and maintains subscriber routing and mobility information on the NIU software. The NIU contains the software that interfaces with the computing module (CM) for maintenance functions. The NIU also gives the XLIU channelized access to the DMS-100 switch network.
Appendix H: ASU background information 181 Figure 44 LPP architecture 2 MS 0 2 MS 1 2 MS 0 2 MS 1 LMS 0 Shelf 0 Rate adapter Shelf 1 F-bus repeater LMS 1 T-bus DS30 2 DS30 ASU 11 F-bus 0 F-bus repeater F-bus repeater F-bus 1 ASU 23 F-bus 0 F-bus repeater F-bus repeater F-bus 1 ASU 24 Rate adapter F-bus repeater F-bus 1 ASU 12 Shelf 3 T-bus F-bus 0 ASU 0 Shelf 2 DS30 ASU 35 The LMS represents the first level of the two-level message switching hierarchy.
Appendix H: ASU background information DMS-bus.
Appendix H: ASU background information 183 Figure 45 SSLPP architecture SR128/256 to MS 0 SR128/256 to MS 1 F-bus 0 F-bus interface F-bus interface F-bus 1 ASU 1 ASU 12 SuperNode SE link interface shelf The SNSE LIS is part of the SuperNode SE configuration. In this arrangement, the SNSE LIS is collocated with a DMS-bus (MS), 16kbyte ENET, CM, and SLM hardware in a single frame. By virtue of the proximity to the MS, there is no need to provide a fiber or DS30 interface with the SNSE LIS.
Appendix H: ASU background information Figure 46 SNSE-LIS architecture Rate adapter MS 0 MS 1 Intershelf F-bus 0 LIS shelf Intershelf F-bus 1 F-bus 0 F-bus repeater F-bus repeater F-bus 1 ASU 1 ENI shelf Rate adapter ASU 12 F-bus 0 F-bus repeater F-bus repeater F-bus 1 ASU 13 297-8991-910 Standard 03.
Appendix I: Obtaining a MAC address This appendix provides information on media access control (MAC) addresses1, and on obtaining a MAC address for the Ethernet interface unit (EIU). Overview The standard among manufacturers of Internetworking hardware is that the MAC address is hard-coded in read-only memory (ROM) on each device. The address becomes a unique identifier, and this standard ensures that no two devices have the same identifier.
Appendix I: Obtaining a MAC address Figure 47 EIU MAC address format I/G 0 U/L 1 Nortel’s vendor ID 2 System dependent field 23 24 27 28 System System-dependent field 31 32 47 The format of the MAC address is defined as follows: • Nortel sets the two bits for the I/G and U/L fields according to the IEEE definition of the MAC address. • For the vendor identifier, Nortel uses the 22-bit identifier that the IEEE assigns (00 0000 0000 0000 1010 1110).
Appendix I: Obtaining a MAC address 187 How to get the MAC address for an EIU Nortel is responsible for assigning blocks of MAC addresses to its customers. CAUTION Possible loss of service Do not assign an arbitrary MAC address to either EIUs or other SuperNode equipment. Duplicate MAC addresses can cause protocol conflicts at the Open Systems Interconnect (OSI) data link or equivalent layer, making equipment unaccessible to the network.
Appendix I: Obtaining a MAC address 297-8991-910 Standard 03.
List of terms ACCS automated calling card system ADAS automated directory assistance service AIN advanced intelligent network ALP application layer program APU application processor unit APUX application processor for Unix ARP address resolution protocol ASU application-specific unit ATF automatic file transfer AUI attachment unit interface BCS batch change supplement BMS buffer management system BMSM BMS manager BOOTP boot protocol CCS7 common channel signaling for SS7 CLASS custom local
List of terms CM computing module CPU central processing unit DATAS DMS Accounting and Traffic Analysis System DCP data communication processor (now EIU) DMS Digital Multiplex System DTMF dual-tone multifrequency E800 enhanced 800 services EIC Ethernet interface card EIP Ethernet interface paddle board EIU Ethernet interface unit EMI electromagnetic interference F-Bus FIFO frame transport bus first in, first out FLIS fiberized link interface shelf FP file processor FRIU frame relay interfa
List of terms 191 IML inter-message switch links InARP IOC IP inverse address resolution protocol input/output controller Internet Protocol IPF integrated processor and F-bus IPX Internet packet exchange ISDN ISG integrated services data network isolated system ground ISN integrated service node ISUP Kbyte integrated user services part kilobyte Kbyte/s kilobyte per second Kbit Kbit/s LAN kilobit kilobit per second local area network LAPB link access protocol - balanced LIS link interface shelf LIU
List of terms MAP maintenance and administration position Mbyte megabyte Mbyte/s megabytes per second Mbit megabits Mbit/s megabits per second MDLP mobile data link protocol MDR7 message detail recording for CSS7 MS message switch MTP message transfer part NIC Network Information Center NFS network file system OM operational measurement OSPF OSI open shortest path first open systems interconnect P-Bus peripheral bus PDU protocol data unit RARP RFC reverse address resolution protocol
List of terms 193 SDM SuperNode Data Manager SEB software engineering bulletin SLM system load module SMP simple management protocol SNA system network architecture SNAP SuperNode access protocol SNSE LIS SuperNode SE link interface shelf SNIP SuperNode IP scheduler class SNIX SuperNode UNIX SNMP simple network management protocol SOS Support Operating System SPM service peripheral module SQE signal quality error SS7 signalling system #7 SSLPP STP single-shelf link peripheral processor signalin
List of terms UDP user datagram protocol ULP upper layer protocol UTP unshielded twisted-pair VPU voice processor unit WAN wide area network WS workstation XDR external data representation XLIU X.25/X.75 link interface unit 297-8991-910 Standard 03.
DMS-100 Family Ethernet Interface Unit User Guide © 1998 Northern Telecom All rights reserved NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern Telecom.
