Cabletron Systems DMS-100 manuel d'utilisation
- Voir en ligne ou télécharger le manuel d’utilisation
- 196 pages
- 0.48 mb
Aller à la page of
Les manuels d’utilisation similaires
-
Network Card
Cabletron Systems 6H259-17
58 pages 0.54 mb -
Network Card
Cabletron Systems 9A128-01
85 pages 0.93 mb -
Network Card
Cabletron Systems FOT-F3
41 pages 0.1 mb -
Network Card
Cabletron Systems Expansion module DELHE-UA
50 pages 0.8 mb -
Network Card
Cabletron Systems W85
60 pages 0.29 mb -
Network Card
Cabletron Systems 38
33 pages 0.35 mb -
Network Card
Cabletron Systems WPIM-RT1
50 pages 0.26 mb -
Network Card
Cabletron Systems HSIM-G01
36 pages 0.25 mb
Un bon manuel d’utilisation
Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Cabletron Systems DMS-100. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Cabletron Systems DMS-100 ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.
Qu'est ce que le manuel d’utilisation?
Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Cabletron Systems DMS-100 décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.
Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.
Donc, ce qui devrait contenir le manuel parfait?
Tout d'abord, le manuel d’utilisation Cabletron Systems DMS-100 devrait contenir:
- informations sur les caractéristiques techniques du dispositif Cabletron Systems DMS-100
- nom du fabricant et année de fabrication Cabletron Systems DMS-100
- instructions d'utilisation, de réglage et d’entretien de l'équipement Cabletron Systems DMS-100
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes
Pourquoi nous ne lisons pas les manuels d’utilisation?
Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Cabletron Systems DMS-100 ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Cabletron Systems DMS-100 et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Cabletron Systems en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Cabletron Systems DMS-100, comme c’est le cas pour la version papier.
Pourquoi lire le manuel d’utilisation?
Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Cabletron Systems DMS-100, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.
Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Cabletron Systems DMS-100. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.
Table des matières du manuel d’utilisation
-
Page 1
297-8991-910 DMS-100 Family Ethernet Interface Unit User Guide TELECOM12 Standard 03.01 August 1999[...]
-
Page 2
[...]
-
Page 3
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 Tele[...]
-
Page 4
iv 297-8991-910 Standard 03.01 August 1999[...]
-
Page 5
DMS-100 Family EIU User Guide TELECOM12 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 des[...]
-
Page 6
vi Publication history 297-8991-910 Standard 03.01 August 1999[...]
-
Page 7
DMS-100 Family EIU User Guide TELECOM12 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 xviii Input prompt (&g[...]
-
Page 8
viii Contents 297-8991-910 Standard 03.01 August 1999 Operational measurements 43 Chapter 2: 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[...]
-
Page 9
Contents ix DMS-100 Family EIU User Guide TELECOM12 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 I[...]
-
Page 10
x Contents 297-8991-910 Standard 03.01 August 1999 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 Addr[...]
-
Page 11
DMS-100 Family EIU User Guide TELECOM12 xi List of figures Figure 1 Overall architecture of enhanced SuperNode system 24 Figure 2 Ethernet interface data flow 26 Figure 3 EIU mapping to lower levels of the OSI communications model 28 Figure 4 Link interface shelf, with 2-slot EIU locations 29 Figure 5 SSLPP, with 2-slot EIU locations 30 Figure 6 DM[...]
-
Page 12
xii 297-8991-910 Standard 03.01 August 1999 Figure 34 Subnet mask: class C 156 Figure 35 IP addressing: class D 157 Figure 36 IP addressing: class E 157 Figure 37 Address mask example 158 Figure 38 Simple network numbering 159 Figure 39 Host configuration 166 Figure 40 Router configurations 167 Figure 41 Host and router configuration 168 Figure 42 [...]
-
Page 13
DMS-100 Family EIU User Guide TELECOM12 xiii List of tables Table 1 DMS-Core feature packages 38 Table 2 DMS-bus port engineering requirements for peripherals 41 Table 3 IP routing table 60 Table 4 IP route list table 60 Table 5 TCP connection limits by SuperNode subsystem 62 Table 6 UDP connection limits by SuperNode subsystem 62 Table 7 Buffer al[...]
-
Page 14
xiv 297-8991-910 Standard 03.01 August 1999 Table 34 FTP operations reference: workstation to DMS 136 Table 35 FTP operations reference: DMS to workstation 138 Table 36 IP address classes 150 Table 37 NIC IP address request form 172[...]
-
Page 15
DMS-100 Family EIU User Guide TELECOM12 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 [...]
-
Page 16
xvi 297-8991-910 Standard 03.01 August 1999 • Commands Refer ence Manual , 297-1001-822 • DMS SuperNode DataSP AN Frame Relay Service Maintenance Guide , 297-51 1 1-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 ([...]
-
Page 17
xvii DMS-100 Family EIU User Guide TELECOM12 • Clarifications and Extensions for the Bootstrap Pr otocol , RFC1542 • File T ransfer Pr otocol , RFC959 • Internet Contr ol Message Pr otocol , RCF792 • Internet Pr otocol , RFC791 • OSPF V ersion 2 , RFC1583 • Reverse Addr ess Resolution Pr otocol , RFC903 • Routing Information Pr otoco[...]
-
Page 18
xviii 297-8991-910 Standard 03.01 August 1999 CAUTION Possibility of equipment damage CAUTION Possibility of static electricity damage DANGER Possibility of personal injury DANGER Possibility of electrocution How commands, parameters, and responses are represented Commands, parameters, and responses in this document conform to the following convent[...]
-
Page 19
xix DMS-100 Family EIU User Guide TELECOM12 Commands and fixed parameters Commands and fixed parameters that are entered at a MAP terminal are shown in uppercase letters: >BSY CTRL ctrl_no V ariables V ariables are shown in lowercase letters: >BSY CTRL ctrl_no The letters or numbers that the variable represents must be entered. Each variabl[...]
-
Page 20
xx 297-8991-910 Standard 03.01 August 1999[...]
-
Page 21
DMS-100 Family EIU User Guide TELECOM12 21 Chapter 1: Introduction to the EIU This chapter describes the Ethernet interface unit (EIU). T opics in the chapter include the following: • overview of the EIU • system architecture • hardware description • limitations and restrictions • feature packaging CAUTION Possible loss of network securit[...]
-
Page 22
22 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 • 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 sw[...]
-
Page 23
Chapter 1: Introduction to the EIU 23 DMS-100 Family EIU User Guide TELECOM12 • 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[...]
-
Page 24
24 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 Figure 1 Overall architecture of enhanced SuperNode system DMS-bus interface and expansion T wo methods are used to interface processing engines to the DMS-bus. Direct links between the processors and the DMS-bus is the primary method for establishing this connection. A s[...]
-
Page 25
Chapter 1: Introduction to the EIU 25 DMS-100 Family EIU User Guide TELECOM12 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 f[...]
-
Page 26
26 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 Figure 2 Ethernet interface data flow Given the cost of the SuperNode cabinet infrastructure, providing the standard hard connection interfaces in this mechanical environment is not possible. For this reason, interfaces are placed outside the boundaries of these cabinets[...]
-
Page 27
Chapter 1: Introduction to the EIU 27 DMS-100 Family EIU User Guide TELECOM12 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[...]
-
Page 28
28 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 Figure 3 EIU mapping to lower levels of the OSI communications model Hardware description The EIU is based on hardware originally developed for the signaling transfer point (STP). One of the main components of the STP is the LPP , which is a frame that can hold up to 36 t[...]
-
Page 29
Chapter 1: Introduction to the EIU 29 DMS-100 Family EIU User Guide TELECOM12 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 P- bus to F-bus interface connects the processor bus with the frame bus, which in turn is connected to the local message swi[...]
-
Page 30
30 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 Figure 5 SSLPP , with 2-slot EIU locations Figure 6 shows the placement of an LPP provisioned with an EIU on a DMS SuperNode switch. Figure 6 DMS SuperNode switch LPP with an EIU Figure 7 shows EIU links to the MS on the fiberized link interface shelf (FLIS). 2-slot ASU [...]
-
Page 31
Chapter 1: Introduction to the EIU 31 DMS-100 Family EIU User Guide TELECOM12 Figure 7 DMS SuperNode FLIS with an EIU 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. [...]
-
Page 32
32 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 Figure 8 Ethernet interface architecture 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. Attachment unit interface—NT9X85[...]
-
Page 33
Chapter 1: Introduction to the EIU 33 DMS-100 Family EIU User Guide TELECOM12 For a 10BaseT twisted-pair LAN, the AUI connection is usually on one side with an RJ-1 1 telephone jack on the other . T ypically , standard office four -wire circuits are used to connect the MAU to the hub. The hub is an electronic replacement for the multiple access pr[...]
-
Page 34
34 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 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 151[...]
-
Page 35
Chapter 1: Introduction to the EIU 35 DMS-100 Family EIU User Guide TELECOM12 — 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 be[...]
-
Page 36
36 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 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 [...]
-
Page 37
Chapter 1: Introduction to the EIU 37 DMS-100 Family EIU User Guide TELECOM12 The Ethernet address in the LIUINV table has the format of the Nortel SuperNode family range of addresses: X 000075F xxxxx , where X is hexadecimal notation and x is a variable. For more information on MAC addresses, refer to “Appendix I: Obtaining a MAC address”. Dia[...]
-
Page 38
38 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 TCP Each TCP connection has its own state machine. For the number of allowed connections, refer to T able 5, TCP connection limits by Supernode subsystem in this document. There are also SOS limitations in that applications that require hundreds or thousands of connection[...]
-
Page 39
Chapter 1: Introduction to the EIU 39 DMS-100 Family EIU User Guide TELECOM12 Software for peripheral processors is controlled through package lists that define the entities for a specific load. The EIU may have several loads depending upon the applications resident on it. As of CSP02, the EIU-related software is packaged in LANCOMM. Software is [...]
-
Page 40
40 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 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. Figure 9 Example of DMS-bus intermessage switch configuration The following cards must also be provisioned on each switch: • a minimum [...]
-
Page 41
Chapter 1: Introduction to the EIU 41 DMS-100 Family EIU User Guide TELECOM12 The information in table 2 defines the port requirements for EIU installation. 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. EIUs are n[...]
-
Page 42
42 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999 — the EIU state • During normal operation, the default EIU routes all messages to the CM. If there is a problem with the default EIU or its links, the following occurs: — the default EIU advertises to the network that it is no longer available (or in the event of a [...]
-
Page 43
Chapter 1: Introduction to the EIU 43 DMS-100 Family EIU User Guide TELECOM12 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. Log reports All logs from the EIU conform to the DMS OAM infrastructure. Log messages are formatted[...]
-
Page 44
44 Chapter 1: Introduction to the EIU 297-8991-910 Standard 03.01 August 1999[...]
-
Page 45
DMS-100 Family EIU User Guide TELECOM12 45 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 telne[...]
-
Page 46
46 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 Software architecture The protocol stack supported on the DMS-core includes the following: • bootstrap protocol (BOOTP) • file transfer protocol (FTP) •I P • telnet • transmission control protocol (TCP) • user datagram protocol (UDP) • simple network manage[...]
-
Page 47
Chapter 2: EIU messaging protocols 47 DMS-100 Family EIU User Guide TELECOM12 Figure 1 1 SuperNode TCP/ IP protocol stack The message flow between SuperNode nodes, and between SuperNode nodes and external Ethernet LAN, is shown in figure 12 in this section. ICMP IP ARP TCP UDP GNI (generic subnet interface) FTS ETHERNET 20, 21 23 161, 162 67, 68 [...]
-
Page 48
48 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 Figure 12 SuperNode TCP/IP message flow Applications TCP/UDP IP FTS DMS-core Applications TCP/UDP IP FTS File processor DMS-bus Applications TCP/UDP IP FTS EIU Ethernet Ethernet LAN Applications TCP IP Ethernet Workstation EIU as router Inter-host connections[...]
-
Page 49
Chapter 2: EIU messaging protocols 49 DMS-100 Family EIU User Guide TELECOM12 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 on[...]
-
Page 50
50 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 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 [...]
-
Page 51
Chapter 2: EIU messaging protocols 51 DMS-100 Family EIU User Guide TELECOM12 detects and sets the record length. T o 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 (negat[...]
-
Page 52
52 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 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 . The IP layer interfaces with the following[...]
-
Page 53
Chapter 2: EIU messaging protocols 53 DMS-100 Family EIU User Guide TELECOM12 The MAPCI supports asynchronous output to both the scroll area and a “full screen” area. The input, however , is buf fered in a line-by-line mode. This combination of features requires that the telnet client perform echoing of input characters. The telnet server trans[...]
-
Page 54
54 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 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 W ithin a single SuperNode switch, multiple ho[...]
-
Page 55
Chapter 2: EIU messaging protocols 55 DMS-100 Family EIU User Guide TELECOM12 “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 no[...]
-
Page 56
56 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 Figure 13 T ypical configuration for LAN and SuperNode subnets 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 T o ensure that the [...]
-
Page 57
Chapter 2: EIU messaging protocols 57 DMS-100 Family EIU User Guide TELECOM12 • 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[...]
-
Page 58
58 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 • Upon failure of any one EIU IP router , the traf fic 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 EI[...]
-
Page 59
Chapter 2: EIU messaging protocols 59 DMS-100 Family EIU User Guide TELECOM12 Figure 14 An example SuperNode Ethernet Workstation Workstation LMS EIU200 EIU201 APUX20 LIU7 CM MS APX LMS EIU100 EIU101 APUX10 LIU7 Ethernet LAN Ethernet LAN Ethernet LAN Router Router[...]
-
Page 60
60 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 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 [...]
-
Page 61
Chapter 2: EIU messaging protocols 61 DMS-100 Family EIU User Guide TELECOM12 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 mor[...]
-
Page 62
62 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 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. The parameter TCP_CONN controls the number of TCP connections for the node. The value for this parameter can be changed[...]
-
Page 63
Chapter 2: EIU messaging protocols 63 DMS-100 Family EIU User Guide TELECOM12 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 [...]
-
Page 64
64 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 • 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 lar ge buffer sizes. These values are load and application dependent. When the TCP[...]
-
Page 65
Chapter 2: EIU messaging protocols 65 DMS-100 Family EIU User Guide TELECOM12 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. For more information on datafill for IP throttling, refer to “Chapter [...]
-
Page 66
66 Chapter 2: EIU messaging protocols 297-8991-910 Standard 03.01 August 1999 IP throttling for SSLPP The SSLPP incorporates additional throttling control for TCP/IP traffic sent over SR256 between the MS and SSLPP . T able 8 shows the recommended traf fic values for entry into table IPTHRON. Adherence to these values ensures adequate bandwidth f[...]
-
Page 67
DMS-100 Family EIU User Guide TELECOM12 67 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. Table 10 Summary of data sc[...]
-
Page 68
68 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 The following sections describe these tables as they apply to EIU provisioning. For complete information on data schema, refer to DMS-100 T ranslations Guide , 297-8xxx-350. Interdependency and auto-configuration T ables IPROUTER and IPHOST are interdependent on each other , as wel[...]
-
Page 69
Chapter 3: EIU datafill 69 DMS-100 Family EIU User Guide TELECOM12 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) Y ou must datafill the EIU in table LIUINV before datafilling it in table IPHOS[...]
-
Page 70
70 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 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 i[...]
-
Page 71
Chapter 3: EIU datafill 71 DMS-100 Family EIU User Guide TELECOM12 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 t[...]
-
Page 72
72 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 EIU MAC addresses By industry convention, MAC addresses for networking devices are unique worldwide. In typical networking devices, the MAC address is burned into a PROM on the circuit pack. However , for EIUs on the DMS-100 switch, the CARDINFO see subfields Card information This f[...]
-
Page 73
Chapter 3: EIU datafill 73 DMS-100 Family EIU User Guide TELECOM12 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 de[...]
-
Page 74
74 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 • 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 sequ[...]
-
Page 75
Chapter 3: EIU datafill 75 DMS-100 Family EIU User Guide TELECOM12 While table 12 provides all the information you need to datafill for EIUs, complete information on table IPNETWRK is in DMS-100 T ranslations Guide , 297-xxxx-350. Table 12 Field descriptions for table IPNETWRK for EIU datafill Field Subfield or refinement Entry Explanation and act[...]
-
Page 76
76 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 PARM SCRNFLAG Parameter. If a screening flag is a requirement, enter SCRNGLAG. Enter refinement SCRNFLAG. DFLT_ INTERFACE EIU_INTERFACE DFLT_GTWY_IP ADDR IOM_ INTERFACE IOP_INTERFACE Y or N NULLPARM To specify an EIU interface as the LAN interface for the CM, enter refinements for W[...]
-
Page 77
Chapter 3: EIU datafill 77 DMS-100 Family EIU User Guide TELECOM12 Sample datafill for table IPNETWRK Figure 16 shows sample datafill for table IPNETWRK for an EIU. Figure 16 Datafill examples for table IPNETWRK SCRNFLAG GTWY_IPADDR IOM_NUM PORT PACKLET Y or N IP address with four numbers from 0 to 255 0 to 255 0 to 255 0 to 255 Screen flag. If [...]
-
Page 78
78 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 Supplementary information The TRANSLA TE command in the NETMAN tool can be used to convert an IP address into network parameters and vice versa. Observe the following criteria required for the subnet: • the subnet size must be the same as the subnet size used on the LAN-side of th[...]
-
Page 79
Chapter 3: EIU datafill 79 DMS-100 Family EIU User Guide TELECOM12 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 T able 13 lists the ?[...]
-
Page 80
80 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 Sample datafill for table IPROUTER Figure 17 shows sample datafill for table IPROUTER for an EIU. Figure 17 Datafill example for table IPROUTER T able IPHOST T able IPHOST assigns the IP addresses to SuperNode end hosts. SuperNode end hosts can have one or two addresses, dependin[...]
-
Page 81
Chapter 3: EIU datafill 81 DMS-100 Family EIU User Guide TELECOM12 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 cor[...]
-
Page 82
82 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 NODENAME = AP If the entry in field NODENAME is AP , enter the data in the following refinements: • SMNINDEX • SNADDR • TCPCONN • FTPCLCON • FTPSVCON • UNIXADDR NODENAME AP, APU, CM , EIU, ELIU, FP,MS Node name Enter the node name: • AP (application processor) • AP[...]
-
Page 83
Chapter 3: EIU datafill 83 DMS-100 Family EIU User Guide TELECOM12 The datafill appears in the following table. NODENAME = APU If the entry in field NODENAME is APU, enter the data in the following refinements: • APUINDEX • SOSADDR • UNIXADDR • TCPCONN • FTPCLCON • FTPSVCON Table 15 Field descriptions for conditional datafill for NOD[...]
-
Page 84
84 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 The datafill appears in the following table. NODENAME = CM If the entry in field NODENAME is CM, enter the data in the following refinements. • CMINDEX • TCPCONN • FTPCLCON • FTPSVCON Table 16 Field descriptions for conditional datafill for NODENAME = APU Field Subfield o[...]
-
Page 85
Chapter 3: EIU datafill 85 DMS-100 Family EIU User Guide TELECOM12 The datafill appears in the following table. NODENAME = EIU If the entry in field NODENAME is EIU, enter data in the following refinements: • EIUINDEX • SNADDR • LANADDR • TCPCONN • FTPCLCON • FTPSVCON Table 17 Field descriptions for conditional data for NODENAME = CM[...]
-
Page 86
86 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 The datafill appears in the following table. NODENAME = ELIU If the entry in field NODENAME is ELIU, enter the data in the following refinements: • ELIUINDEX • SNADDR • LANADDR • TCPCONN Table 18 Field descriptions for conditional datafill for NODENAME = EIU Field Subfiel[...]
-
Page 87
Chapter 3: EIU datafill 87 DMS-100 Family EIU User Guide TELECOM12 The datafill appears in the following table. NODENAME = FP If the entry in field NODENAME is FP , enter data in the following refinements. • SMNINDEX • SNADDR • TCPCONN • FTPCLCON • FTPSVCON • UNIXADDR Table 19 Field descriptions for conditional datafill for NODENAME [...]
-
Page 88
88 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 The datafill appears in the following table. NODENAME = MS If the entry in field NODENAME is MS, enter the data in the following refinements. • MSINDEX • SNADDR • TCPCONN • FTPCLCON • FTPSVCON Table 20 Field descriptions for conditional datafill for NODENAME = FP Field [...]
-
Page 89
Chapter 3: EIU datafill 89 DMS-100 Family EIU User Guide TELECOM12 The datafill appears in the following table. Sample datafill for table IPHOST Figure 18 shows sample datafill for table IPHOST for an EIU. Figure 18 Datafill example for table IPHOST T able IPTHRON T able IPTHRON contains the IP throttling numbers that control congestion. The IP[...]
-
Page 90
90 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 • 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 data?[...]
-
Page 91
Chapter 3: EIU datafill 91 DMS-100 Family EIU User Guide TELECOM12 For more information on throttling, refer to“IP throttling” on page 61 and to the Pr ovisioning 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 [...]
-
Page 92
92 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 OPTION see subfield Option This field consists of subfield SNNODE. 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 n[...]
-
Page 93
Chapter 3: EIU datafill 93 DMS-100 Family EIU User Guide TELECOM12 Sample datafill for table IPTHRON Figure 19 shows sample datafill for table IPTHRON for an EIU. Figure 19 Datafill example for table IPTHRON T able IPPROTO T able IPPROT O is rarely used and normally does not need to be datafilled. EIUINDEX 0 to 750 Ethernet interface unit index[...]
-
Page 94
94 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 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 T able 23 lists the fields and value[...]
-
Page 95
Chapter 3: EIU datafill 95 DMS-100 Family EIU User Guide TELECOM12 T able ENSITES T able ENSITES contains a complete list of all sites referenced in table EXNDINV . Datafill sequence and implications There are no datafill sequence and implications. Datafill T able 24 lists the fields and value ranges used to datafill an EIU in table ENSITES. W[...]
-
Page 96
96 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 While table 25 provides all the information you need to datafill for EIUs, complete information on table ENTYPES is in DMS-100 T ranslations Guide , 297-xxxx-350. Sample datafill for table ENTYPES Figure 22 shows sample datafill for table ENTYPES for an EIU. Figure 22 Datafill e[...]
-
Page 97
Chapter 3: EIU datafill 97 DMS-100 Family EIU User Guide TELECOM12 T able 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 T able EXNDINV filters IP packets Datafill se[...]
-
Page 98
98 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 Datafill T able 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 T ranslations Guide , 297-xxxx-350. Table 26 Field descr[...]
-
Page 99
Chapter 3: EIU datafill 99 DMS-100 Family EIU User Guide TELECOM12 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. M[...]
-
Page 100
100 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 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 n[...]
-
Page 101
Chapter 3: EIU datafill 101 DMS-100 Family EIU User Guide TELECOM12 EN0LKALM 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[...]
-
Page 102
102 Chapter 3: EIU datafill 297-8991-910 Standard 03.01 August 1999 Sample datafill for table EXNDINV Figure 24 shows sample datafill for table EXNDINV for an EIU. Figure 24 Datafill example for table EXNDINV 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 p[...]
-
Page 103
DMS-100 Family EIU User Guide August 1999 103 Chapter 4: EIU maintenance This chapter provides information on Ethernet interface unit (EIU) maintenance. EIU maintenance is limited to hardware diagnostics for the Ethernet interface card (EIC) and the Ethernet interface paddle board (EIP). The maintenance procedures do not include detection or isolat[...]
-
Page 104
104 Chapter 4: EIU maintenance 297-8991-910 Standard 03.01 August 1999 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 actio[...]
-
Page 105
Chapter 4: EIU maintenance 105 DMS-100 Family EIU User Guide TELECOM12 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 [...]
-
Page 106
106 Chapter 4: EIU maintenance 297-8991-910 Standard 03.01 August 1999 T able 27 summarizes the preset bucket parameters for reported LAN faults. EIU overload control In an overload situation, the EIU overload control discards packets at the interrupt level rather than at the process level. The feedback scheme is devised such that packets received [...]
-
Page 107
Chapter 4: EIU maintenance 107 DMS-100 Family EIU User Guide TELECOM12 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 personn[...]
-
Page 108
108 Chapter 4: EIU maintenance 297-8991-910 Standard 03.01 August 1999 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 redundan[...]
-
Page 109
Chapter 4: EIU maintenance 109 DMS-100 Family EIU User Guide TELECOM12 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 [...]
-
Page 110
110 Chapter 4: EIU maintenance 297-8991-910 Standard 03.01 August 1999 For information and procedures, refer to Car d Replacement Pr ocedur es , 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 1[...]
-
Page 111
DMS-100 Family EIU User Guide TELECOM12 111 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[...]
-
Page 112
112 Appendix A: EIU installation checklist 297-8991-910 Standard 03.01 August 1999 Use the list in table 28 as a checklist to ensure that you meet all installation requirements for hardware, software, and datafill. Table 28 EIU installation checklist Item description Contact Check Hardware EIU hardware (NTEX22, NT9X84, NT9X85) circuit packs (one e[...]
-
Page 113
DMS-100 Family EIU User Guide TELECOM12 113 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. CAUTION Possible loss of network security Using the Ethernet i[...]
-
Page 114
114 Appendix B: EIU troubleshooting 297-8991-910 Standard 03.01 August 1999 T ools T able 29 summarizes the tools available for troubleshooting the EIU. For more information on these tools, refer to Commands Refer ence Manual , 297-1001-822. T roubleshooting checklist Much of the troubleshooting required for the EIU is handled at the frame, shelf, [...]
-
Page 115
Appendix B: EIU troubleshooting 115 DMS-100 Family EIU User Guide TELECOM12 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 SuperNode- based nodes 4, 5, 6 Cannot log in as the admin user 7, 8 Cannot setup an FTP sessi[...]
-
Page 116
116 Appendix B: EIU troubleshooting 297-8991-910 Standard 03.01 August 1999[...]
-
Page 117
DMS-100 Family EIU User Guide 03.01 117 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[...]
-
Page 118
118 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 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[...]
-
Page 119
Appendix C: Using FTP 119 DMS-100 Family EIU User Guide TELECOM12 <bin/txt> is the transfer type, txt for ASCII or bin for BINAR Y <record length> the logical record length is a number from 1 to 32767 This file format is shown in table 31. If the filename extension is not as described in table 31, the system attempts to identify the e[...]
-
Page 120
120 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 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 err or message: ‘503 TYPE must be Binary.’ ‘503 TYPE must be ASCII.’ V olume listing The FTP application provides t[...]
-
Page 121
Appendix C: Using FTP 121 DMS-100 Family EIU User Guide TELECOM12 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 [...]
-
Page 122
122 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 Obtaining the IP address of the SuperNode host 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 att[...]
-
Page 123
Appendix C: Using FTP 123 DMS-100 Family EIU User Guide TELECOM12 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 T utorial: basic FTP operations This section provides a set of procedures for using FTP on [...]
-
Page 124
124 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 where passwd is a valid user password for the userID that you are using Y ou are placed in the default directory . Example of a MAP response: 230 User johnh logged in. 4 Y ou have completed this procedure. Procedure 2 Determining your directory location Step Action 1 Establish an FTP[...]
-
Page 125
Appendix C: Using FTP 125 DMS-100 Family EIU User Guide TELECOM12 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 512 Jan 26 08:05 News drwx------ 2 paulg snopc 512 Feb 2 07:55 PERSONAL -rw-r--r-- 1 paulg gtest 397 Jan 4 [...]
-
Page 126
126 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 2 Y ou have completed this procedure. T utorial: 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. It describes the command lines for the following FTP operations: • setting file type to ASC[...]
-
Page 127
Appendix C: Using FTP 127 DMS-100 Family EIU User Guide TELECOM12 5 Determine the next step. 6 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 Dete[...]
-
Page 128
128 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 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 rename[...]
-
Page 129
Appendix C: Using FTP 129 DMS-100 Family EIU User Guide TELECOM12 12 Y ou 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 Change directory on the remote host by typing ft[...]
-
Page 130
130 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 where path_name is a valid directory path Example: ftp> lcd ‘/S00DTEMP’ 7 Determine the next step. 8 Set the record length of the file by typing ftp> lrecl rec_length and pressing the Enter key . where rec_length is the record length required for the file Example: ftp>[...]
-
Page 131
Appendix C: Using FTP 131 DMS-100 Family EIU User Guide TELECOM12 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 Y ou have completed this procedure. T utorial: advanced [...]
-
Page 132
132 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 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[...]
-
Page 133
Appendix C: Using FTP 133 DMS-100 Family EIU User Guide TELECOM12 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 [...]
-
Page 134
134 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 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 . where user_id is the user_[...]
-
Page 135
Appendix C: Using FTP 135 DMS-100 Family EIU User Guide TELECOM12 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>commandm[...]
-
Page 136
136 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 T able 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 lo[...]
-
Page 137
Appendix C: Using FTP 137 DMS-100 Family EIU User Guide TELECOM12 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). The above command sequence • sets the [...]
-
Page 138
138 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 T able 35 shows FTP operations for sessions started on a DMS-100 switch for connection to a workstation. In this scenario, the DMS-100 switch is the local host and the workstation is the remote host. Send an image file to the DMS WS> binary WS> site lrecl 1020 WS>put file_na[...]
-
Page 139
Appendix C: Using FTP 139 DMS-100 Family EIU User Guide TELECOM12 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. Change the working directory on the DMS CM> lcd ?[...]
-
Page 140
140 Appendix C: Using FTP 297-8991-910 Standard 03.01 August 1999 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[...]
-
Page 141
DMS-100 Family EIU User Guide TELECOM12 141 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 ([...]
-
Page 142
142 Appendix D: Using telnet 297-8991-910 Standard 03.01 August 1999 T elnet access to a switch Procedure 12 T elnetting 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 . 3 List available EIUs by typing >list all and p[...]
-
Page 143
Appendix D: Using telnet 143 DMS-100 Family EIU User Guide TELECOM12 Procedure 13 T elnetting 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 typin[...]
-
Page 144
144 Appendix D: Using telnet 297-8991-910 Standard 03.01 August 1999[...]
-
Page 145
DMS-100 Family EIU User Guide TELECOM12 145 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[...]
-
Page 146
146 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 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 cam[...]
-
Page 147
Appendix E: Understanding IP and IP addressing 147 DMS-100 Family EIU User Guide TELECOM12 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[...]
-
Page 148
148 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 Figure 26 Simple network map 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 [...]
-
Page 149
Appendix E: Understanding IP and IP addressing 149 DMS-100 Family EIU User Guide TELECOM12 Figure 27 Detailed network diagram Choosing IP addresses IP was originally developed to allow large numbers of diverse institutions to interconnect their local hosts and networks into a larger network (an Internetwork). In time, a larger entity connecting man[...]
-
Page 150
150 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 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[...]
-
Page 151
Appendix E: Understanding IP and IP addressing 151 DMS-100 Family EIU User Guide TELECOM12 T wo 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. Network address 127 is not a val[...]
-
Page 152
152 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 Figure 29 IP addressing: class A | | 72 4 32 networkid hostid bits | hostid bits bits 1 bit 2 to 22 bits For any class, the hostid can be split into a subnet id and a hostid depending on customer requirements. This helps simplify routing to areas. For class A[...]
-
Page 153
Appendix E: Understanding IP and IP addressing 153 DMS-100 Family EIU User Guide TELECOM12 Figure 30 Subnet mask: class A Base_T el-10 IPNETWRK No. subnets No. hosts netmask Netmask in binary format subnet size 2 4194302 255.192.0.0 (11111111.11000000.00000000.00000000) 2 6 2097150 255.224.0.0 (11111111.11100000.00000000.00000000) 3 14 1048574 255.[...]
-
Page 154
154 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 Figure 31 IP addressing: class B | | 14 32 networkid hostid bits | hostid bits 2 bit 2 to 14 bits Class B indicator | | | subnet id || | 2 to 14 bits 10 therefore, we can have 16384-2 class B networks each with 65536-2 hosts (if no subnets). Class B addresses[...]
-
Page 155
Appendix E: Understanding IP and IP addressing 155 DMS-100 Family EIU User Guide TELECOM12 Figure 32 Subnet mask: class B Base_T el-12 IPNETWRK No. subnets No. hosts netmask Netmask in binary format subnet size 2 16382 255.255.192.0 (11111111.11111111.11000000.00000000) 2 6 8190 255.255.224.0 (11111111.11111111.11100000.00000000) 3 14 4090 255.255.[...]
-
Page 156
156 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 Figure 33 IP addressing: class C Figure 34 Subnet mask: class C | | 21 32 networkid hostid bits | hostid bits 3 bit 2 to 6 bits Class C indicator | | | subnet id || | 2 to 6 bits 110 therefore, we can have 16384-2 class C networks each with 65536-2 hosts (if [...]
-
Page 157
Appendix E: Understanding IP and IP addressing 157 DMS-100 Family EIU User Guide TELECOM12 Figure 35 IP addressing: class D Figure 36 IP addressing: class E Address masks For administrative or procedural reasons, a network number can be subdivided into subnetworks using a subnetwork mask, also called a subnet or address mask. A network mask is a se[...]
-
Page 158
158 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 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 . T o reserve the third byte for the subnetwork number , they use subnetwork mask 255.255.255.0. Figure 37 o[...]
-
Page 159
Appendix E: Understanding IP and IP addressing 159 DMS-100 Family EIU User Guide TELECOM12 Figure 38 Simple network numbering 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 or ganization. The Corporate Networkin[...]
-
Page 160
160 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 representative to discuss state-of-the-art secure data communications equipment products. V ariable-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 connecte[...]
-
Page 161
Appendix E: Understanding IP and IP addressing 161 DMS-100 Family EIU User Guide TELECOM12 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 s[...]
-
Page 162
162 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999 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 deter[...]
-
Page 163
Appendix E: Understanding IP and IP addressing 163 DMS-100 Family EIU User Guide TELECOM12 • 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 [...]
-
Page 164
164 Appendix E: Understanding IP and IP addressing 297-8991-910 Standard 03.01 August 1999[...]
-
Page 165
DMS-100 Family EIU User Guide TELECOM12 165 Appendix F: EIU supported configurations This appendix provides examples of EIU supported configurations.[...]
-
Page 166
166 Appendix F: EIU supported configurations 297-8991-910 Standard 03.01 August 1999 Figure 39 Host configuration TABLE LIUINV EIU 1 LIM 0 1 26 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17009 TABLE IPNETWRK 0 47 105 150 1 12 $ (SCRNFLAG N) $ TABLE IPHOST 0 CM 0 64 32 32 1 EIU 1 47 105 150 2 47 105 144 2 32 8 8 Number of TCP connections Number [...]
-
Page 167
Appendix F: EIU supported configurations 167 DMS-100 Family EIU User Guide TELECOM12 Figure 40 Router configurations TABLE LIUINV EIU 1 LIM 0 1 26 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17009 EIU 2 LIM 0 2 14 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17015 TABLE IPNETWRK 0 47 105 150 1 12 (EIU 1) $ (SCRNFLAG N) $ TABLE IPHOST 0 CM 0 64 [...]
-
Page 168
168 Appendix F: EIU supported configurations 297-8991-910 Standard 03.01 August 1999 Figure 41 Host and router configuration Can be another subnet or new network on this side of external router TABLE LIUINV EIU 1 LIM 0 1 26 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17009 EIU 2 LIM 0 2 14 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17015 TABL[...]
-
Page 169
Appendix F: EIU supported configurations 169 DMS-100 Family EIU User Guide TELECOM12 Figure 42 Interface configuration part 1 TABLE LIUINV EIU 1 LIM 0 1 26 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17009 EIU 2 LIM 0 2 14 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17015 TABLE IPNETWRK 1 47 105 150 1 12 $ (EIU_INTERFACE EIU 1) (DFLT_INTERFACE[...]
-
Page 170
170 Appendix F: EIU supported configurations 297-8991-910 Standard 03.01 August 1999 Figure 43 Interface Configuration part 2 TABLE LIUINV EIU 1 LIM 0 1 26 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17009 EIU 2 LIM 0 2 14 ERS09BB NTEX22BB NT9X84AA NT9X85AA YES 000075F17015 TABLE IPNETWRK 1 47 105 150 1 12 $ (EIU_INTERFACE EIU 1) (DFLT_INTERFACE[...]
-
Page 171
DMS-100 Family EIU User Guide TELECOM12 171 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 [...]
-
Page 172
172 Appendix G: IP network number requests 297-8991-910 Standard 03.01 August 1999 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. Based on network topology , the following information [...]
-
Page 173
Appendix G: IP network number requests 173 DMS-100 Family EIU User Guide TELECOM12 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 h[...]
-
Page 174
174 Appendix G: IP network number requests 297-8991-910 Standard 03.01 August 1999 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 establishi[...]
-
Page 175
Appendix G: IP network number requests 175 DMS-100 Family EIU User Guide TELECOM12 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 networ[...]
-
Page 176
176 Appendix G: IP network number requests 297-8991-910 Standard 03.01 August 1999[...]
-
Page 177
DMS-100 Family EIU User Guide TELECOM12 177 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)[...]
-
Page 178
178 Appendix H: ASU background information 297-8991-910 Standard 03.01 August 1999 OSI router or support host services. The current list of router and host services that use dedicated EIUs include: • automated directory assistance service (ADAS) • billing server • cellular digital packet data (CDPD) • programmable service node (PSN) • aut[...]
-
Page 179
Appendix H: ASU background information 179 DMS-100 Family EIU User Guide TELECOM12 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 withou[...]
-
Page 180
180 Appendix H: ASU background information 297-8991-910 Standard 03.01 August 1999 • 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 interf[...]
-
Page 181
Appendix H: ASU background information 181 DMS-100 Family EIU User Guide TELECOM12 Figure 44 LPP architecture The LMS represents the first level of the two-level message switching hierarchy . The LMS provides the interface between the F-bus seen by individual ASUs and services and non-channelized DS30 links to the DMS- bus. The LMS is duplicated: [...]
-
Page 182
182 Appendix H: ASU background information 297-8991-910 Standard 03.01 August 1999 DMS-bus. While the rate adapter is responsible for mediating traffic flow between the F-bus and T -bus, the T -bus provides the following functionality: • T -bus for inter- and intra-LPP messaging (inter -LPP messaging is carried on DS30 links) • access to mapp[...]
-
Page 183
Appendix H: ASU background information 183 DMS-100 Family EIU User Guide TELECOM12 Figure 45 SSLPP architecture 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 proxim[...]
-
Page 184
184 Appendix H: ASU background information 297-8991-910 Standard 03.01 August 1999 Figure 46 SNSE-LIS architecture F-bus 0 F-bus 1 F-bus 0 F-bus 1 ENI shelf LIS shelf Rate adapter MS 0 F-bus repeater ASU 1 F-bus repeater ASU 12 F-bus repeater ASU 13 F-bus repeater ASU 14 Intershelf F-bus 0 MS 1 Rate adapter Intershelf F-bus 1[...]
-
Page 185
DMS-100 Family EIU User Guide TELECOM12 185 Appendix I: Obtaining a MAC address This appendix provides information on media access control (MAC) addresses 1 , 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 [...]
-
Page 186
186 Appendix I: Obtaining a MAC address 297-8991-910 Standard 03.01 August 1999 Figure 47 EIU MAC address format 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[...]
-
Page 187
Appendix I: Obtaining a MAC address 187 DMS-100 Family EIU User Guide TELECOM12 How to get the MAC address for an EIU Nortel is responsible for assigning blocks of MAC addresses to its customers. T o obtain MAC addresses, contact your Nortel Engineering support group by using the internal Nortel email address, MAC ADDRESS2. This process is document[...]
-
Page 188
188 Appendix I: Obtaining a MAC address 297-8991-910 Standard 03.01 August 1999[...]
-
Page 189
DMS-100 Family EIU User Guide TELECOM12 189 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 [...]
-
Page 190
190 List of terms 297-8991-910 Standard 03.01 August 1999 CM computing module CPU central processing unit DATAS DMS Accounting and T raffic 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 [...]
-
Page 191
List of terms 191 DMS-100 Family EIU User Guide TELECOM12 IML inter-message switch links InARP inverse address resolution protocol IOC input/output controller IP Internet Protocol IPF integrated processor and F-bus IPX Internet packet exchange ISDN integrated services data network ISG isolated system ground ISN integrated service node ISUP integrat[...]
-
Page 192
192 List of terms 297-8991-910 Standard 03.01 August 1999 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 [...]
-
Page 193
List of terms 193 DMS-100 Family EIU User Guide TELECOM12 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 netwo[...]
-
Page 194
194 List of terms 297-8991-910 Standard 03.01 August 1999 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[...]
-
Page 195
[...]
-
Page 196
DMS-100 Family Ethernet Interface Unit User Guide © 1998 Northern T elecom All rights reserved NORTHERN TELECOM CONFIDENTIAL : The information contained in this document is the property of Northern T elecom. Except as specifically authorized in writing by Northern T elecom, the holder of this document shall keep the information contained herein c[...]