Specifications

ManualsBrandsDigital Media ManualsComputer equipmentDECmau 900TL

DEChub

Network Configuration

Part Number: EK-CONFG-CG. A01

October 1996

This manual describes platforms and modules used to build networks.

Summary of content (300 pages)

PAGE 1
DEChub Network Configuration Part Number: EK-CONFG-CG. A01 October 1996 This manual describes platforms and modules used to build networks.
PAGE 2
Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description.
PAGE 3
Contents Preface .................................................................. ix 1 Platforms 1.1 1.2 1.3 1.4 1.5 1.6 Platform Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEChub 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEChub 900 MultiSwitch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital MultiStack System . . . . .
PAGE 4
3.7 3.8 3.9 3.10 3.11 3.12 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62 Concentrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65 Network Access Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74 Management Agents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 5
A.2 A.3 A.4 A.5 A.6 A.7 A.8 A.9 A.10 A.11 A.12 A.13 A.14 A.15 A.16 A.17 B A-4 A-5 A-6 A-7 A-8 A-9 A-10 A-11 A-14 A-17 A-25 A-31 A-33 A-35 A-38 A-39 FDDI Overview B.1 B.2 B.3 B.4 B.5 B.6 B.7 B.8 C Dual Ring Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tree Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DECconcentrator 900MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 6
Figures 1–1 1–2 1–3 1–4 1–5 3–1 3–2 3–3 3–4 3–5 3–6 3–7 3–8 3–9 3–10 3–11 3–12 3–13 3–14 3–15 3–16 3–17 3–18 3–19 3–20 3–21 3–22 3–23 3–24 3–25 3–26 3–27 3–28 3–29 3–30 3–31 3–32 3–33 3–34 3–35 3–36 6–1 6–2 6–3 vi DEChub 90 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DEChub 900 MultiSwitch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Digital MultiStack System . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 7
6–4 6–5 6–6 6–7 6–8 6–9 6–10 6–11 6–12 6–13 6–14 6–15 6–16 A–1 A–2 A–3 A–4 A–5 A–6 A–7 A–8 A–9 A–10 A–11 A–12 A–13 A–14 A–15 A–16 A–17 A–18 A–19 A–20 A–21 A–22 A–23 A–24 A–25 A–26 A–27 A–28 A–29 A–30 A–31 A–32 A–33 Multi-Ethernet Hub, LAN Interconnect Window . . . . . . . . . . . . . . . . . . . . . . Multi-Ethernet Backbone Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Central Department LAN Interconnect Window . . . . . . . . . . . . . . . . . . . . . . .
PAGE 8
B–1 B–2 B–3 B–4 B–5 B–6 B–7 FDDI Dual Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Station Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDDI Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wrapped FDDI Ring . . . . . . . . . . . . . . .
PAGE 9
Preface About this Manual This manual describes the products used to build and configure networks. The intent is to provide a summary of the products that are available. Intended Audience This manual has two major audiences: • Pre-sales technical support—includes Digital’s technical sales force and Value Added Resellers (VARs). • Post-sales support—includes Digital’s Multivendor Customer Service personnel and Digital’s customers.
PAGE 10
Structure of This Manual This book is structured as follows: • • • Chapter 1 presents an overview of the available platforms. • • Chapter 4 describes network management methods used. • • • • Chapter 6 contains example networks. Chapter 2 provides selection information for the products. Chapter 3 lists and describes network modules available for use with the platforms. Chapter 5 describes the network management software tools available to manage the network.
PAGE 11
Online Services To locate product specific information, refer to the following online services: BBS To read the Bulletin Board System, set your modem to 8 bits, no parity, 1 stop bit and dial 508-486-5777 (U.S.) WWW The Digital Equipment Corporation Network Products Business Home Page on the World Wide Web is located at the following addresses: North America: http://www.networks.digital.com Europe: http://www.networks.europe.digital.com Australia: http://www.digital.com.
PAGE 12
Firmware Updates Digital continuously improves the quality of products through periodic firmware releases. To ensure the high quality and interoperability of products, you should always use the latest available versions of firmware. FTP Location You can get information about the latest firmware releases from your local Digital reseller or your local Digital Sales Office. You can also get this information by reading the README file found in the /pub/DEC/hub900 directory at ftp.digital.com.
PAGE 13
1 Platforms This chapter describes the DEChub and Digital MultiStack System hardware platforms. 1.1 Platform Types Digital provides a variety of hardware platforms including: • • • • • The DEChub 90 The DEChub 900 MultiSwitch The Digital MultiStack System The DEChub ONE The DEChub ONE-MX.
PAGE 14
1.2 DEChub 90 1.2 DEChub 90 The DEChub 90 chassis is designed to support the communication needs of small to mid-size work groups. Figure 1–1 displays the DEChub 90 with modules installed. Built as an Ethernet-based backplane, the DEChub 90 chassis provides mounting, power, and backplane ThinWire Ethernet connection to accommodate up to eight half-height modules. These modules include repeaters, network access servers, bridges, and wide area routers.
PAGE 15
1.
PAGE 16
1.3 DEChub 900 MultiSwitch 1.3 DEChub 900 MultiSwitch The DEChub 900 MultiSwitch chassis is a multitechnology hub that provides support ranging from simple LAN connectivity to high-speed switching. It offers high-performance network access, flexible configuration, superior network management, and security. Figure 1–2 displays the DEChub 900 with modules installed.
PAGE 17
1.
PAGE 18
1.3 DEChub 900 MultiSwitch Features 1–6 • Provides bandwidth on demand with an aggregate throughput of more than 3Gb/s. • Supports multiple bus, ring, and cell-based connections in a several combinations (Ethernet, Token Ring, FDDI, and ATM). Including: – One ThinWire Ethernet, two Token Rings, and one flexible channel on the upper (48-pin) connector. – Fourteen flexible channels on the lower (160-pin) connector. • • Software reconfigurable backplane connections.
PAGE 19
1.4 Digital MultiStack System 1.4 Digital MultiStack System The Digital MultiStack System is a stackable hub system that allows you to use repeaters, internetworking, wireless, LAN monitoring, and management modules in stackable network configurations. The Digital MultiStack System can stack up to sixteen modules, commonly referred to as half-height modules. It can be rack mounted in a standard 19-inch rack, or distributed throughout a building.
PAGE 20
1.4 Digital MultiStack System An optional attachment unit interface (AUI) connector is available for the DECrepeater 90T-16 to facilitate connections to a network backbone. Because the Digital MultiStack System integrates SNMP management via a separate management channel, it ensures management access by maintaining a continuously available management connection, even if a connection is lost to one of the stackable hubs.
PAGE 21
1.5 DEChub ONE 1.5 DEChub ONE The DEChub ONE is an Ethernet-only single-slot hub that provides standalone capability for full-height network modules. The DEChub ONE provides dc power to the attached module. An attachment unit interface (AUI) on the DEChub ONE can be used to connect the attached module to a standard Ethernet backbone. An optional medium attachment unit (MAU) can be connected to the DEChub ONE AUI to connect it to a fiber-optic, ThinWire, or twisted-pair Ethernet LAN.
PAGE 22
1.6 DEChub ONE-MX 1.6 DEChub ONE-MX The DEChub ONE-MX is a single-slot hub that provides standalone capability for full-height network modules. An attachment unit interface (AUI) on the DEChub ONE-MX can connect an attached network module to a standard Ethernet backbone. An optional medium attachment unit (MAU) can be connected to the DEChub ONEMX AUI to connect it to a fiber-optic, ThinWire, or twisted-pair Ethernet LAN.
PAGE 23
1.
PAGE 24
PAGE 25
2 Selecting Products This chapter contains tables that list the platform and network module characteristics. 2.1 Platform Selection Use Table 2–1 to select the platform that meets your requirements.
PAGE 26
2.2 Repeater Module Selection 2.2 Repeater Module Selection Use Tables 2-2, 2-3, and 2-4 to select the repeater module that meets your requirements. Table 2–2 DECrepeater Half-Height Modules (Twisted Pair and Coaxial) 2–2 Criteria DECrepeater 90T16 DECrepeater 90TS DECrepeater 90C DECrepeater 90T+ Platform DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack.
PAGE 27
2.2 Repeater Module Selection Criteria DECrepeater 90T16 DECrepeater 90TS DECrepeater 90C DECrepeater 90T+ Eavesdrop Protection No Yes No No Authorized Address No Two authorized addresses belonging to the same station per port. No No Redundancy No No No No Address Learning Yes Yes Yes Yes Comments No longer shipped.
PAGE 28
2.2 Repeater Module Selection 2–4 Criteria DECrepeater 90FA DECrepeater 90FL DECrepeater 90FS Traffic Counters No No Standard repeater counters. (No internal LAN or Flex Channel counters.) Port Switching Module level, one internal LAN. Module level, one internal LAN. Module level, one internal LAN. Intrusion Detection No No Log error on intrusion, disable port on intrusion Eavesdrop Protection No No Yes Authorized Address No No Two addresses belonging to the same station per port.
PAGE 29
2.2 Repeater Module Selection Table 2–4 DECrepeater Full-Height Modules Criteria DECrepeater 900TM DECrepeater 900GM Platform DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. Port Configuration Thirty two 10BaseT, one AUI in the DEChub ONE or DEChub ONE-MX. Twenty four 10BaseT (TELCO), one AUI in the DEChub ONE or DEChub ONE-MX. Manageability Embedded SNMP agent. Fully manageable in any platform.
PAGE 30
2.3 PORTswitch Module Selection 2.3 PORTswitch Module Selection Use Table 2–5 to select the PORTswitch module that meets your requirements. Table 2–5 PORTswitch Full-Height Modules Criteria PORTswitch 900TP PORTswitch 900CP PORTswitch 900FP Platform DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. Port Configuration Thirty two 10BaseT, one AUI, one AUI in the DEChub ONE or DEChub ONE-MX.
PAGE 31
2.3 PORTswitch Module Selection Criteria PORTswitch 900TP PORTswitch 900CP PORTswitch 900FP Authorized Address Sixteen addresses per 4 ports. Sixteen addresses per 4 ports. Two addresses belonging to the same station, per port. Redundancy Yes Yes Yes Address Learning Yes Yes Yes Comments Port group equals two ports.
PAGE 32
2.4 Bridge Module Selection 2.4 Bridge Module Selection Use Table 2–6 to select the bridge module that meets your requirements. Table 2–6 DECbridge Half-Height Modules 2–8 Criteria DECbridge 90 DECbridge 90FL Platform DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack. Port Configuration One 10Base2, one AUI when standalone. One 10BaseFL/FOIRL, one AUI when standalone.
PAGE 33
2.5 Switch Module Selection 2.5 Switch Module Selection Use Table 2–7 to select the switch module that meets your requirements. Table 2–7 PEswitch/DECswitch Modules Criteria PEswitch 900TX DECswitch 900EE DECswitch 900EF DECswitch 900FO Platform DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX.
PAGE 34
2.5 Switch Module Selection Criteria 2–10 DECswitch 900EE DECswitch 900EF DECswitch 900FO Supports IP Yes Packet Fragmentation (RFC 791 and RFC 1191) Not applicable Yes Yes Supports Full Translation of Packets Between FDDI and Ethernet (IEEE802.1i) Yes Not applicable Yes Yes Specialized Support for Nontranslating Protocols (IEEE802.
PAGE 35
2.6 Concentrator Module Selection 2.6 Concentrator Module Selection Use Table 2–8 to select the concentrator module that meets your requirements. Table 2–8 DECconcentrator Modules Criteria DECconcentrator 900MX DECconcentrator 900TH DECconcentrator 900FM Platform DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. Port Configuration Six front panel ports and two backplane ports.
PAGE 36
2.7 Brouter Module Selection 2.7 Brouter Module Selection Use Table 2–9 to select the brouter module that meets your requirements. Table 2–9 DECbrouter Modules 2–12 Criteria DECbrouter 90T1 DECbrouter 90T2 DECbrouter 90T2A Platform DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack. Port Configuration One 10Base2, one 10BaseT, and one 1x50 WAN port.
PAGE 37
2.7 Brouter Module Selection Criteria DECbrouter 90T1 DECbrouter 90T2 DECbrouter 90T2A Bridging 802.1d, Filtering, LAT Compression. 802.1d, Filtering, LAT Compression. 802.1d, Filtering, LAT Compression. IP Services No No No Comments Best used for connecting to remote Cisco routers. Best used for connecting to remote Cisco routers. Best used for connecting to remote Cisco routers.
PAGE 38
2.8 Router Module Selection 2.8 Router Module Selection Use Table 2–10 to select the router module that meets your requirements. Table 2–10 DECwanrouter Modules 2–14 Criteria DECwanrouter 90 DECwanrouter 90-EW Platform DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack. Port Configuration One 10Base2, one 10BaseT, and one 1x50 Multistandard WAN port (2x64 Kb/s).
PAGE 39
2.9 Network Access Server Module Selection 2.9 Network Access Server Module Selection Use Table 2–11 or Table 2–12 to select the network access server module that meets your requirements. Table 2–11 DECserver Half-Height Modules Criteria DECserver 90L+ DECserver 90TL DECserver 90M Platform DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack. DEChub 90, DEChub 900, standalone, or Digital MultiStack. Port Configuration Eight 6-pin MMJ.
PAGE 40
2.9 Network Access Server Module Selection Table 2–12 DECserver Full-Height Modules 2–16 Criteria DECserver 900TM DECserver 900GM Platform DEChub 900, DEChub ONE, or DEChub ONE-MX. DEChub 900, DEChub ONE, or DEChub ONE-MX. Port Configuration Thirty two 8-pin MJ. Four 68-pin “bulk” connectors. Manageability Embedded SNMP agent. Fully manageable in any platform. Manageable via its own IP address. Embedded SNMP agent. Fully manageable in any platform. Manageable via its own IP address.
PAGE 41
2.10 Token Ring Module Selection 2.10 Token Ring Module Selection Use Table 2–13 to select the token ring module that meets your requirements. Table 2–13 Token Ring Modules Criteria DECmau 900TH DECrepeater 900SL DECrepeater 900TL DECrepeater 900FL Platform DEChub 900 DEChub 900 DEChub 900 DEChub 900 Port Configuration Twenty four 8pin MJ. Two 8-pin MJ and one 10BaseT. Two DB9 and one 10BaseT. Two ST-type fiber optic, and two 8-pin MJ on the rear cover. Manageability Embedded SNMP agent.
PAGE 42
PAGE 43
3 Network Modules This chapter contains detailed information about the network modules. 3.1 Network Module Types Network modules are classified according to application, network type, and size. Applications are determined by module function. Network types are existing standards. Size indicates the module’s size (full-height or half-height) and use in the platforms.
PAGE 44
3.2 Repeaters Modules are provided in two sizes: • Half-height modules are designed for use in either the DEChub 90, the DEChub 900 MultiSwitch or the Digital MultiStack System. • Full-height modules are designed for use in the DEChub 900 MultiSwitch. Not all module sizes are provided for all applications and network types. NOTE Most half-height modules are packaged with a back cover and power supply for standalone use.
PAGE 45
3.2 Repeaters • Eavesdrop protection is provided by sending data packets to the port of the destination address only. All other ports receive scrambled data. • Intrusion protection, logs violations or disables the port. • • • • • • • Dual port redundancy. Integral SNMP agent. Hot swap capability. Front panel LEDs for power, network activity, and port status. In-band and out-of-band management capabilities. Automatic module self-test at power up.
PAGE 46
3.2 Repeaters 3.2.1 DECrepeater 90T+ The DECrepeater 90T+ is an eight port IEEE 802.3 10BaseT-compliant repeater that is used for connecting personal computers, workstations, or any twisted-pair device to an Ethernet LAN. It provides one backplane ThinWire port. It also includes a ThinWire 10Base2 port connector (ThinWire BNC) on the side panel (available when installed in the stacking unit or standalone). Figure 3–1 shows the DECrepeater 90T+ network module.
PAGE 47
3.2 Repeaters Media Eight-pin MJ unshielded twisted-pair (UTP) station connectors. LAN Connectivity • One ThinWire BNC when in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when standalone. Upgrade Method Not field upgradeable.
PAGE 48
3.2 Repeaters 3.2.2 DECrepeater 90T-16 The DECrepeater 90T-16 is a16-port IEEE 802.3 10BaseT-compliant repeater that is used for connecting personal computers, workstations, or any twisted-pair device to an Ethernet LAN. It provides one backplane ThinWire port. It also includes a ThinWire 10Base2 port connector (ThinWire BNC) on the side panel (available when installed in a stacking unit or standalone). Figure 3–2 shows the DECrepeater 90T-16 network module.
PAGE 49
3.2 Repeaters Media Sixteen 8-pin MJ unshielded twisted-pair (UTP) connectors. LAN Connectivity • Both a ThinWire BNC and an attachment unit interface (AUI) available when installed in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when standalone. Upgrade Method Not field upgradable.
PAGE 50
3.2 Repeaters 3.2.3 DECrepeater 90TS The DECrepeater 90TS is an eight-port 802.3 10BaseT repeater with built-in SNMP management and Ethernet port security that is used for connecting personal computers, workstations, or any twisted-pair device to an Ethernet LAN. The unit has a ThinWire 10Base2 port connector (ThinWire BNC) on the side panel.
PAGE 51
3.2 Repeaters Media Eight 8-pin MJ unshielded twisted-pair (UTP) connectors. LAN Connectivity • One ThinWire BNC when installed in Digital MultiStack System • Backplane access to a ThinWire segment and/or the flex channel when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC or one AUI (requires the back cover) when standalone. Upgrade Method • Flash Loader. • TFTP via the setup port.
PAGE 52
3.2 Repeaters Features 3–10 • Has per port security for eavesdropping and intrusion protection. • Can serve as the stack manager and SNMP proxy agent for other repeaters. • Supports two addresses per port, allowing for both a physical and DECnet address to be seen and recorded.
PAGE 53
3.2 Repeaters 3.2.4 DECrepeater 900GM The DECrepeater 900GM module is an 802.3 10BaseT (two 50- pin twisted-pair Telco connectors), 24-port repeater designed for use with either 100 ohm shielded (STP) or unshielded (UTP) twisted-pair wire. In addition, an AUI connector provided on the front bezel supports connection to 10Base5 (thick wire) backbones.
PAGE 54
3.2 Repeaters Protocol Ethernet 802.3 Media Two 50-pin twisted pair Telco connectors supporting 24 total (2x12) STP/UTP ports, and one AUI 10Base5 port. LAN Connectivity • When installed in the DEChub 900 MultiSwitch, the module can be connected to the ThinWire Ethernet LAN and/or any one of the six flex channels. Also one AUI on the front panel. • Two AUIs when installed in the DEChub ONE or DEChub ONE-MX. Upgrade Method • Flash Loader. • TFTP via the Setup port.
PAGE 55
3.2 Repeaters – Alarms – Events IP Service Provides IP Services. Features • Has per port security for eavesdropping and intrusion protection. • Supports two addresses per port, allowing for both a physical and DECnet address to be seen and recorded. • Offers per port statistics for monitoring repeater traffic.
PAGE 56
3.2 Repeaters 3.2.5 DECrepeater 900TM The DECrepeater 900TM module is an 802.3 10BaseT (twisted- pair) 32-port repeater designed for use with either 100 ohm shielded (STP) or unshielded twistedpair (UTP) wire. Figure 3–5 shows the DECrepeater 900TM network module. Figure 3–5 DECrepeater 900TM Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.
PAGE 57
3.2 Repeaters Media Thirty two 8-pin MJ ports using either 100 ohm shielded or unshielded twisted-pair. LAN Connectivity • When installed in the DEChub 900 MultiSwitch, the module can be connected to the ThinWire Ethernet LAN and/or any one of the six flex channels. • One AUI when installed in the DEChub ONE or DEChub ONE-MX. Upgrade Method • Flash Loader • TFTP via the Setup port Manageability • Digital MultiStack System—Not installable.
PAGE 58
3.2 Repeaters IP Service Provides IP Services. Features 3–16 • Has per port security for intrusion/eavesdropping protection. • Supports two addresses per port, allowing for both a physical and DECnet address to be seen and recorded.
PAGE 59
3.2 Repeaters 3.2.6 DECrepeater 90FA The DECrepeater 90FA module is a three-port repeater that provides low-cost connections to 10BaseFL /FOIRL fiber using ST-type fiber optic connectors, ThinWire, and an AUI connector. Used as a standalone unit, it provides a fiber optic link between two Ethernet LANs. It can also connect a standard Ethernet backbone and ThinWire segment.
PAGE 60
3.2 Repeaters Platform This half-height module is used in the: • Digital MultiStack System • DEChub 900 MultiSwitch • DEChub 90 • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 Media One fiber optic port, one AUI connector. LAN Connectivity • One ThinWire BNC and either one AUI or one fiber optic (ST-type) when installed in Digital MultiStack System • One backplane ThinWire and either one AUI or one fiber optic (ST-type) in a DEChub 900 MultiSwitch.
PAGE 61
3.2 Repeaters • DEChub ONE-MX—Not installable. • Standalone—Not manageable. Supported MIBs • Ethernet MIB (RFC 1398) • Repeater MIB (RFC 1516) • Digital Extended Repeater MIB • MIB II (RFC 1213) IP Service Not an IP Services provider.
PAGE 62
3.2 Repeaters 3.2.7 DECrepeater 90FL The DECrepeater 90FL module is an 802.3 10BaseFL/FOIRL multiport fiber optic repeater with four ST-type fiber ports. It also includes a ThinWire 10Base2 port connector on the side panel (available when installed in the stacking unit or standalone). Figure 3–7 shows the DECrepeater 90FL network module Figure 3–7 DECrepeater 90FL Platform This half-height module is used in the: • Digital MultiStack System. • DEChub 900 MultiSwitch. • DEChub 90.
PAGE 63
3.2 Repeaters LAN Connectivity • One ThinWire BNC when installed in the Digital MultiStack System • One backplane ThinWire in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when installed standalone. Upgrade Method Not field upgradeable. Manageability • Digital MultiStack System—Requires the DECagent 90, the DECrepeater 90TS, or DECrepeater 90FS as the stack manager for local and remote management.
PAGE 64
3.2 Repeaters 3.2.8 DECrepeater 90FS The DECrepeater 90FS module is an 802.3 10BaseFL/FOIRL repeater with two fiber ports, one AUI connector, and one 10Base2 port (available when installed in the stacking unit or standalone). Figure 3–8 shows the DECrepeater 90FS network module. The module allows you to connect three different media types. Its two 10BaseFL/ FOIRL fiber ports can be configured either as a redundant port or as two separate fiber ports.
PAGE 65
3.2 Repeaters • DEChub 90 • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 Media Two 10BaseFL/FOIRL-compliant using ST-type fiber optic connectors, and one AUI. LAN Connectivity • One ThinWire BNC or one AUI when installed in the Digital MultiStack System • Provides backplane access to a ThinWire segment and/or the flex channel in the DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90.
PAGE 66
3.2 Repeaters • Digital Extended Repeater MIB • DEChub 900 Public Common MIB IP Service Provides IP Services. Features 3–24 • Offers two fiber ports which may be configured as one redundant port • Has per port security for eavesdropping and intrusion protection. • Can serve as the stack manager and SNMP proxy agent for other repeaters. • Supports two addresses per port, allowing for both a physical and DECnet address to be seen and recorded.
PAGE 67
3.2 Repeaters 3.2.9 DECrepeater 90C The DECrepeater 90C module is a compact, seven-port repeater that connects PCs and workstations to a ThinWire 802.3/Ethernet LAN. The DECrepeater 90C module has six ThinWire ports for connecting Ethernet segments, and a ThinWire port to connect to a coaxial cable Ethernet backbone. Up to 29 stations can be attached to each port. Figure 3–9 shows the DECrepeater 90C network module.
PAGE 68
3.2 Repeaters Media Six 10Base2 ports (BNC coaxial connectors). LAN Connectivity • One ThinWire BNC when installed in the Digital MultiStack System • One backplane ThinWire in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when installed standalone. Upgrade Method Not field upgradeable.
PAGE 69
3.3 Port Switches 3.3 Port Switches PORTswitch modules are high-density Ethernet modules that support configuration switching on a port group or per-port basis. Per-port configuration switching provides the flexibility to logically group any individual or combination of externally accessible ports to any of six internal LAN segments.
PAGE 70
3.3 Port Switches • • Automatic module self-test at power up. One hop when the repeater is connected to a DEChub 900 MultiSwitch flex channel. Two hops when connected to the backplane ThinWire. The following PORTswitch modules are available.
PAGE 71
3.3 Port Switches 3.3.1 PORTswitch 900TP The PORTswitch 900TP module is a 32 port 802.3 10BaseT port-switching repeater. The module allows per-port switching capability to link a port or group of ports to a LAN segment in DEChub 900 MultiSwitch. Figure 3–10 shows the PORTSwitch 900TP network module. Figure 3–10 PORTswitch 900TP Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.
PAGE 72
3.3 Port Switches LAN Connectivity • Each port or group of ports is assignable to one of six flex channels and/or the backplane ThinWire in the DEChub 900 MultiSwitch. • One AUI when installed in a DEChub ONE or DEChub ONE-MX. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the module’s built in SNMP agent or through the integral hub management agent. • DEChub 90—Not installable.
PAGE 73
3.3 Port Switches Features • Has 32 10BaseT ports that can operate on one LAN or as up to 6 separate port pairs. The port pairs can be assigned independently to any of six backplane LANs (in the DEChub 900 MultiSwitch). Using clearVISN, you can assign the port pairs as redundant links to other devices. • Has per port security for eavesdropping and intrusion protection. • Supports up to 13 addresses per port, allowing for both a physical and DECnet address to be seen and recorded.
PAGE 74
3.3 Port Switches 3.3.2 PORTswitch 900CP The PORTswitch 900CP module is a 16 port 802.3 10Base2 port-switching repeater. The module allows per-port switching capability to link a port or port group to a LAN segment in a DEChub 900 MultiSwitch. Figure 3–11 shows the PORTswitch 900CP network module. Figure 3–11 PORTswitch 900CP Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.
PAGE 75
3.3 Port Switches LAN Connectivity • Each port or group of ports is assignable to one of six flex channels and/or the backplane ThinWire in the DEChub 900 MultiSwitch. • One AUI when installed in a DEChub ONE or DEChub ONE-MX. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the module’s built in SNMP agent or through the integral hub management agent. • DEChub 90—Not installable.
PAGE 76
3.3 Port Switches Features 3–34 • Has per port security for eavesdropping and intrusion protection. • Supports up to 13 addresses per port, allowing for both a physical and DECnet address to be seen and recorded. • Supports Out-of-Band Management, which provides an SNMP path in addition to normal in-band management by using the Serial Line Internet Protocol (SLIP) through the OBM port on the DEChub ONE or DEChub ONE-MX. • Provides security and statistics capability. • Supports RMON.
PAGE 77
3.3 Port Switches 3.3.3 PORTswitch 900FP The PORTswitch 900FP module is an 802.3 10BaseFL/FOIRL port-switching repeater with 12 fiber ports that can be configured as 6 pairs of redundant ports, 12 individual fiber ports, or in any combination. The module is ideally suited for collapsed fiber backbones, or where redundancy is required. When configured with redundant ports, the PORTswitch 900FP module’s automatic failover capability provides additional reliability.
PAGE 78
3.3 Port Switches Protocol Ethernet 802.3 Media Twelve ST-type fiber optic connectors. LAN Connectivity • Each redundant pair or group is assignable to one of six flex channels and/or the backplane ThinWire in the DEChub 900 MultiSwitch. • One AUI when installed in a DEChub ONE or DEChub ONE-MX. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable.
PAGE 79
3.3 Port Switches – Events IP Service Provides IP Services. Features • Has twelve fiber-optic ports that can operate on one LAN or as up to 6 separate port pairs. The port pairs can be assigned independently to any of six backplane LANs (in the DEChub 900 MultiSwitch). Using clearVISN, you can assign the port pairs as redundant links to other devices. • Has per port security for eavesdropping and intrusion protection.
PAGE 80
3.4 Bridges 3.4 Bridges The DECbridge 90 family of bridges are full-performance IEEE 802.1D compliant Ethernet bridges that connect departmental work groups to larger local area network (LAN) backbones. These bridges keep local network traffic within the work group LAN as they forward traffic that has a destination elsewhere on the backbone. This minimizes work group traffic from impacting overall network performance. The DECbridge 90 automatically configures itself for operation with any IEEE 802.
PAGE 81
3.4 Bridges 3.4.1 DECbridge 90 The DECbridge 90 connects to the backbone using ThinWire Ethernet or AUI transceiver cable. The AUI can support various transmission media such as coaxial and fiber optic cables by use of an optional MAU. Figure 3–13 shows the DECbridge 90 network module. You can be connected to either the ThinWire or the AUI, but not both simultaneously. The active connection is determined by a slide switch on the front of the module.
PAGE 82
3.4 Bridges • DEChub 900 MultiSwitch • DEChub 90 • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 Media One AUI or 10Base2/ThinWire LAN Connectivity • One ThinWire BNC or one AUI when installed in the Digital MultiStack System • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC or one AUI when standalone. Upgrade Method MOP only.
PAGE 83
3.4 Bridges Features • Automatically configures itself for operation with any IEEE 802.
PAGE 84
3.4 Bridges 3.4.2 DECbridge 90FL The DECbridge 90FL module is a fiber optic version of the DECbridge 90 product. It is a local Ethernet-to-Ethernet 10BaseFL/FOIRL-compliant bridge that combines reliability and high-performance in one compact module. Designed to link a departmental work group to the larger LAN backbone, it features AUI and 10Base FL/FOIRL compliant ST fiber optic backbone connections, and a ThinWire coaxial connector for work groups. Figure 3–14 shows the DECbridge 90FL network module.
PAGE 85
3.4 Bridges Platform This half-height module is used in the: • Digital MultiStack System • DEChub 900 MultiSwitch • DEChub 90. • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 Media One AUI or 10BaseFL/FOIRL. LAN Connectivity • One ThinWire BNC or one AUI when installed in the Digital MultiStack System • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90.
PAGE 86
3.4 Bridges IP Service Not an IP Services provider. Features 3–44 • Automatically configures itself for operation with any IEEE 802.
PAGE 87
3.5 Switches 3.5 Switches Switches bring the benefits of full performance 802.1D compliant switching to a range of network applications on a variety of levels - the desktop, the department, and the enterprise. Features • Provides full 802.1D compliant standards-based switching platforms for data integrity and interoperability. • Supports full translation of packets between Ethernet and FDDI (IEEE 802.
PAGE 88
3.5 Switches 3.5.1 PEswitch 900TX The PEswitch 900TX product is a full 802.1D compliant, six-port switched (personal, 10 Mb/s) Ethernet to FDDI switch. It combines full-performance switched Ethernet and guaranteed packet integrity with high-performance FDDI server/ network connectivity. Figure 3–15 shows the PEswitch 900TX network module. The ports are: • Six front panel 10BaseT (8-pin MJ) Ethernet ports with internal crossover.
PAGE 89
3.5 Switches Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.3 and FDDI. Media Six 8-pin MJ ports (either 100 ohm shielded or unshielded twisted-pair). LAN Connectivity • Up to six Ethernet connections on the DEChub 900 MultiSwitch flex channels. One FDDI connection in the DEChub 900 MultiSwitch backplane. Port 3 can be connected to the backplane ThinWire. • One AUI when installed in a DEChub ONE.
PAGE 90
3.5 Switches Supported MIBs • Ethernet MIB (RFC 1398) • FDDI MIB (RFC 1512) • Bridge MIB (RFC 1493) • DEChub 900 Public Common MIB • MIB II (RFC 1213) IP Service Provides IP Services. Features 3–48 • Offers a dedicated 10-Mb channel per user with a connection to a high-speed link (FDDI). • Supports up to 64 addresses across the six Ethernet ports.
PAGE 91
3.5 Switches 3.5.2 DECswitch 900EE The DECswitch 900EE product is a six-port, SNMP manageable Ethernet backbone switch, providing switching capability between each of the six Ethernets. It supports all the filtering capabilities (source MAC address, destination MAC address, protocol type) as well as providing a large address table (8,000 entries). It is also fully IEEE 802.1D bridge compliant. Figure 3–16 shows the DECswitch 900EE network module.
PAGE 92
3.5 Switches Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.3 Media Two AUI and a four 8-pin MJ. LAN Connectivity • Each Ethernet port is independently assignable to either one DEChub 900 MultiSwitch backplane ThinWire or flex channel, or to a dedicated front panel port. Therefore any combination of backplane and front panel connections not exceeding six is allowed.
PAGE 93
3.5 Switches Supported MIBs • Ethernet MIB (RFC 1398) • FDDI MIB (RFC 1512) • Bridge MIB (RFC 1493) • DEChub 900 Public Common MIB • MIB II (RFC 1213) IP Service Provides IP Services. Features • Offers a user-setable rate limiting broadcast and multicast packets by address and specified protocol. • Supports full performance filtering between all of its six ports, at full Ethernet speeds (14,880 packets /seconds/Ethernet).
PAGE 94
3.5 Switches 3.5.3 DECswitch 900EF The DECswitch 900EF product is a high-throughput, SNMP manageable, multiport network switch solution for linking Ethernet with FDDI LANs. Figure 3–17 shows the DECswitch 900EF network module. The DECswitch 900EF module is a “line speed” Ethernet to FDDI IEEE 802.1Dcompliant switch for the backbone. It has six Ethernet switched ports and one FDDI port, providing full switching capability among each of the six Ethernets and an FDDI LAN.
PAGE 95
3.5 Switches Figure 3–17 DECswitch 900EF Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.3 and FDDI Media Six total Ethernet ports, two AUI and four 8-pin MJ modular jacks (either 100 ohm shielded or unshielded twisted-pair). One DAS FDDI port.
PAGE 96
3.5 Switches LAN Connectivity • Each Ethernet port is independently assignable to either one DEChub 900 MultiSwitch backplane ThinWire or flex channel, or to a dedicated front panel port. Therefore any combination of backplane and front panel connections not exceeding six is allowed. Port 3 can be switched to the backplane ThinWire • The Standalone port 4 can be switched to the DEChub ONE AUI. • The Standalone port 4 can be switched to the DEChub ONE-MX AUI.
PAGE 97
3.5 Switches – Events IP Service Provides IP Services. Features • Supplies a seven-port bridge, providing six Ethernet to Ethernet ports (2 AUI and four 8-pin MJ modular jacks) plus one DAS FDDI port • Supports full performance filtering between all of its ports, at full Ethernet speeds (14,880 packets/seconds /Ethernet). • Provides a minimum filtering rate of more than 460,000 pps on the FDDI port. • Provides a high-performance forwarding rates with an aggregate output of 62,000 pps.
PAGE 98
3.5 Switches 3.5.4 DECswitch 900FO The DECswitch 900FO six-port Ethernet to FDDI Level 2 switch provides highperformance switching between Ethernet and FDDI networks. The DECswitch 900FO has six front panel fiber optic ST-type ports and one FDDI logical rear backplane port. Each of the six Ethernet ports is individually software configurable using clearVISN to connect either through: • • • The front panel ports. One of six backplane Ethernet segments of a DEChub 900 MultiSwitch.
PAGE 99
3.5 Switches Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.3 and FDDI Media Six total Ethernet ports (ST-type). LAN Connectivity • Each Ethernet port is independently assignable to either one DEChub 900 MultiSwitch backplane ThinWire or flex channel, or to a dedicated front panel port. Therefore any combination of backplane and front panel connections not exceeding six is allowed.
PAGE 100
3.5 Switches Supported MIBs • Ethernet MIB (RFC 1398) • FDDI MIB (RFC 1512) • Bridge MIB (RFC 1493) • DEChub 900 Public Common MIB • MIB II (RFC 1213) • RMON – Statistics – History – Alarms – Events IP Service Provides IP Services.
PAGE 101
3.6 Brouters 3.6 Brouters Digital has an interoperable family of flexible, full- function local, and wide area network multiprotocol brouters. The following modules are available for use in the DEChub platforms or as standalone devices. • • • DECbrouter 90T1 DECbrouter 90T2 DECbrouter 90T2A 3.6.1 DECbrouter 90T1, 90T2, and 90T2A The DECbrouter 90T provides a multiprotocol internetworking solution for linking small and medium sized Ethernet networks.
PAGE 102
3.6 Brouters Figure 3–19 DECbrouter 90T1 and DECbrouter 90T2 Platform This half-height module is used in the: • Digital MultiStack System • DEChub 900 MultiSwitch • DEChub 90 • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 and WAN. Media One or two “mini-cinch” connectors using a BC12 cable. The cable supports various modem connections. LAN Connectivity 3–60 • One ThinWire BNC when in the Digital MultiStack System.
PAGE 103
3.6 Brouters • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when standalone. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Managed through the module’s built in SNMP agent. • DEChub 900 MultiSwitch—Managed through the module’s built in SNMP agent. • DEChub 90—Managed through the module’s built in SNMP agent. • DEChub ONE—Not installable. • DEChub ONE-MX—Not installable.
PAGE 104
3.7 Routers 3.7 Routers Digital has an interoperable family of flexible, full-function local, and wide area network multiprotocol routers. The following two modules are available for use in the DEChub platforms or as a standalone device: • • DECwanrouter 90-802.3/Ethernet to a single 64 Kb/s port. DECwanrouter 90EW-802.3/Ethernet to two 64 Kb/s ports. 3.7.
PAGE 105
3.7 Routers Platform These half-height modules are used in the: • Digital MultiStack System • DEChub 900 MultiSwitch • DEChub 90 • When used standalone, they require a separate power unit. Protocol Ethernet 802.3 Media One “mini-cinch” connector using a BC12 cable. LAN Connectivity • One ThinWire BNC when in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90.
PAGE 106
3.7 Routers Supported MIBs • DEChub 900 Public Common MIB • MIB II (RFC 1213) IP Service Not IP Services providers. Features 3–64 • Route TCP/IP, Novell IPX, DECnet, and OSI CLNP. • Support DDCMP, HDLC, ANS X.25 data link protocols.
PAGE 107
3.8 Concentrators 3.8 Concentrators The FDDI concentrators provide for the attachment of devices such as workstations, systems, bridges, routers, or other concentrators to the FDDI network. The following modules are available for use in the DEChub platforms or as standalone device. • • • DECconcentrator 900MX DECconcentrator 900TH DECconcentrator 900FH NOTE Appendix A contains details on FDDI Configuration Options. 3.8.
PAGE 108
3.8 Concentrators Figure 3–21 DECconcentrator 900MX Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol FDDI Media Single-Mode Fiber (SMF), Multi-Mode Fiber (MMF), and Unshielded twisted-pair (UTP). LAN Connectivity The module is configurable to connect either through: • 3–66 The front panel ports.
PAGE 109
3.8 Concentrators • Two backplane FDDI ports on the DEChub 900 MultiSwitch. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the module’s built in SNMP agent or through the integral hub management agent. • DEChub 90—Not installable. • DEChub ONE—Managed through the module’s built in SNMP agent. • DEChub ONE-MX—Managed through the module’s built in SNMP agent.
PAGE 110
3.8 Concentrators 3.8.2 DECconcentrator 900TH The DECconcentrator 900TH has fourteen FDDI ports on the front panel. Twelve ports are fixed Unshielded twisted-pair (UTP). Two ports are Physical Media dependent (modPMDs). The following modPMDs are available: • • • Multimode fiber (ANSI MIC and SC connector) Single mode fiber (ST and SC connector) Unshielded twisted-pair (UTP) NOTE Refer to Appendix A for details on FDDI configuration options for the module.
PAGE 111
3.8 Concentrators Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol FDDI Media Two modPMDs and twelve Unshielded twisted-pair (UTP). LAN Connectivity The module is configurable to connect either through: • The front panel ports. • Two backplane FDDI ports on the DEChub 900 MultiSwitch. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable.
PAGE 112
3.8 Concentrators Supported MIBs • FDDI MIB (RFC 1512) • DEChub 900 Public Common MIB • MIB II (RFC 1213) IP Service Provides IP Services. Features 3–70 • Can connect directly to a dual ring or to a tree in a hub backplane. • Provides flexible modular media options. • Offers maximum configuration flexibility with sixteen total ports; two are software configurable as FDDI A, B, M, or S ports. • Contains an optical bypass port (OBR) for use with OBP relays.
PAGE 113
3.8 Concentrators 3.8.3 DECconcentrator 900FH The DECconcentrator 900FH has fourteen FDDI ports on the front panel. Twelve ports are fixed Multimode fiber (SC connector). Two ports are Physical Media dependent (modPMDs). The following modPMDs are available: • • • Multimode fiber (ANSI MIC and SC connector) Single mode fiber (ST and SC connector) Unshielded twisted-pair (UTP) NOTE Refer to Appendix A, for details on FDDI configuration options for the module.
PAGE 114
3.8 Concentrators Platform This full-height module is used in the: • DEChub 900 MultiSwitch • DEChub ONE • DEChub ONE-MX. Protocol FDDI Media Two modPMDs and twelve Multi-Mode fiber) LAN Connectivity The module is configurable to connect either through: • The front panel ports. • Two backplane FDDI ports on the DEChub 900 MultiSwitch. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable.
PAGE 115
3.8 Concentrators • MIB II (RFC 1213) IP Service Provides IP Services. Features • Can connect directly to a dual ring in a hub backplane. • Provides flexible modular media options. • Offers maximum configuration flexibility with six total ports; four are software configurable as FDDI A, B, or M ports. • Contains an optical bypass port (OBR) for use with OBP relays.
PAGE 116
3.9 Network Access Servers 3.9 Network Access Servers Network Access Servers connect terminals, printers, or personal computers, to hosts on an Ethernet LAN. Communication servers connect asynchronous devices at speeds up to 115.2 Kb/s to local nodes. They can also provide remote access (dial-in) and modem pool (dial-out) support for remote personal computers. The following modules are available for use in the DEChub platforms or as standalone devices.
PAGE 117
3.9 Network Access Servers 3.9.1 DECserver 90TL The DECserver 90TL access server is designed for high-speed asynchronous connections to UNIX, ULTRIX, OpenVMS, DOS, and multivendor network services. This eight-port multisession Telnet/LAT access server offers industrystandard connections at speeds of up to 57.6 Kb/s. It supports TCP/IP, Telnet, LAT, SLIP, CSLIP, and PPP protocols (with a 4 Mb memory upgrade), as well as management systems including SNMP, TSM V1.
PAGE 118
3.9 Network Access Servers Platform This half-height module is used in the: • Digital MultiStack System • DEChub 900 MultiSwitch • DEChub 90 • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 Media Eight 8-pin MJ8 connectors. LAN Connectivity • One ThinWire BNC when in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90.
PAGE 119
3.9 Network Access Servers Supported MIBs • Ethernet MIB (RFC 1398) • DEChub 900 Public Common MIB • MIB II (RFC 1213) • AppleTalk MIB (RFC 1243) • Character MIB (RFC 1316) • RS232-Like MIB (RFC 1317) • Ethernet-Like MIB (RFC 1284) • PPP/LCP MIB (RFC 1471) • IPX MIB (Novell) IP Service Not an IP Services provider. Features • ThinWire 10Base2 port connector (ThinWire BNC) on the side panel.
PAGE 120
3.
PAGE 121
3.9 Network Access Servers 3.9.2 DECserver 90L+ The DECserver 90L+ is an eight-port LAT-only protocol terminal server that connects video terminals, printers, and personal computers, to the Ethernet network environment. It supports up to four sessions per port and provides full 38.4 Kb/s line speeds. Figure 3–25 DECserver 90L+ Platform This half-height module is used in the: • Digital MultiStack System • DEChub 900 MultiSwitch • DEChub 90 • When used standalone it requires a separate power unit.
PAGE 122
3.9 Network Access Servers LAN Connectivity • One ThinWire BNC when in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when standalone. Upgrade Method • Not upgradeable. Manageability • Digital MultiStack System—Managed through the DECagent 90. • DEChub 900 MultiSwitch—Managed through the DECagent 90. • DEChub 90—Managed through the DECagent 90.
PAGE 123
3.9 Network Access Servers • • – Digital’s clearVISN for management of servers in a DEChub environment. – MOP (Maintenance Operation Protocol) Multiple levels of security for managing and controlling user access Accounting—provides event logging of significant user actions (Not available on the DECserver 90L+.
PAGE 124
3.9 Network Access Servers 3.9.3 DECserver 90M The DECserver 90M is an enhanced eight-port multiprotocol communications server that supports LAT, TCP/IP, Telnet, SLIP, CSLIP, and PPP. The module supports up to eight sessions per port and line speeds up to 57.6 Kb/s. The DECserver 90M provides connections to most modems and printers supporting data leads as well as DSR/DTR control signals. The DECserver 90M also includes a 10BaseT network port in addition to the ThinWire port.
PAGE 125
3.9 Network Access Servers Protocol Ethernet 802.3 Media Eight 8-pin MJ connectors. LAN Connectivity • One ThinWire BNC when in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when standalone. Upgrade Method • Reprogrammable via BOOTP/TFTP. Update initiated via a physical console terminal or Telnet remote console. Fall back to downline load at power up.
PAGE 126
3.9 Network Access Servers • Ethernet-Like MIB (RFC 1284) • PPP/LCP MIB (RFC 1471) • IPX MIB (Novell) IP Service Provides IP Services (V2.0 or later). Features • ThinWire 10Base2 port connector (ThinWire BNC) on the side panel, 10BaseT connector on the front panel. • Out-of-Band Management that provides an SNMP path in addition to normal inband management by using the Serial Line Internet Protocol (SLIP) through the OBM connector on the DEChub 900 MultiSwitch.
PAGE 127
3.9 Network Access Servers 3.9.4 DECserver 900TM The DECserver 900TM is a 32-port Network Access Server that connects asynchronous devices including terminals, printers, modems, or personal computers to an Ethernet LAN. The module is configured with 32 8-pin MJ connectors and provides software selectable limited modem control.
PAGE 128
3.9 Network Access Servers • DEChub ONE-MX. Protocol Ethernet 802.3 Media Thirty-two 8-pin MJ, either shielded or unshielded twisted-pair. LAN Connectivity • When installed in the DEChub 900 MultiSwitch, the module can be connected to the ThinWire Ethernet LAN and/or any one of the six flex channels. • One AUI when installed in the DEChub ONE or DEChub ONE-MX. Upgrade Method • Flash RAM is optional. If present, may be reprogrammed via BOOTP/TFTP.
PAGE 129
3.9 Network Access Servers • Ethernet-Like MIB (RFC 1284) • PPP/LCP MIB (RFC 1471) • IPX MIB (Novell) IP Service Provides IP Services (V2.0 or later). Features • Out-of-Band Management that provides an SNMP path in addition to normal inband management by using the Serial Line Internet Protocol (SLIP) through the OBM connector on the DEChub 900 MultiSwitch. • Host Multiplexing for remote node or remote control access.
PAGE 130
3.9 Network Access Servers 3.9.5 DECserver 900GM The DECserver 900GM is a 32-port Network Access Server that connects asynchronous devices including terminals, printers, modems, or personal computers to an Ethernet LAN. The module is configured with four “bulk”connectors (A through D) and provides software selectable limited or full modem control, depending on the cable used.
PAGE 131
3.9 Network Access Servers • DEChub ONE • DEChub ONE-MX. Protocol Ethernet 802.3 Media Four “bulk” connectors (68 pin high density). LAN Connectivity • When installed in the DEChub 900 MultiSwitch, the module can be connected to the ThinWire Ethernet LAN and/or any one of the six flex channels. • One AUI when installed in the DEChub ONE or DEChub ONE-MX. Upgrade Method • Downline load at each power up. Nonvolatile flash memory is optional. If present, may be reprogrammed via BOOTP/TFTP.
PAGE 132
3.9 Network Access Servers • Character MIB (RFC 1316) • RS232-Like MIB (RFC 1317) • Ethernet-Like MIB (RFC 1284) • PPP/LCP MIB (RFC 1471) • IPX MIB (Novell) IP Service Provides IP Services (using V2.0 or later). Features • Optional nonvolatile flash memory using the PCMCIA card slot. • Out-of-Band Management that provides an SNMP path in addition to normal inband management by using the Serial Line Internet Protocol (SLIP) through the OBM connector on the DEChub 900 MultiSwitch.
PAGE 133
3.10 Management Agents 3.10 Management Agents A management agent acts as a proxy for devices requiring external SNMP support. The agent responds to SNMP queries on behalf of those devices. The following module is available for use in the DEChub platforms or as standalone device. • DECagent 90 3.10.1 DECagent 90 The DECagent 90 is a Simple Network Management Protocol (SNMP) proxy agent. Specifically the module provides SNMP support for those modules that do not have an integral agent.
PAGE 134
3.10 Management Agents • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 Media Not applicable LAN Connectivity • One ThinWire BNC when installed in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWIre BNC when standalone. Upgrade Method • Flash Loader • TFTP via the Setup port.
PAGE 135
3.10 Management Agents IP Service Not an IP Services provider. Features • Management of multiple DEChub 90s with a single management module and selected standalone modules. One DECagent 90 per eight interconnected or 16 standalone DEChub 90 units or 64 standalone modules on the same LAN. • ThinWire 10Base2 port connector (ThinWire BNC) on the side panel.
PAGE 136
3.11 Token Ring 3.11 Token Ring Digital provides a full range of network modules to create token ring local area networks. These LANs allow the user at the desktop to access the full computing power of the organization through distributed processing. Available network modules provide reliable configuration flexibility for shielded, screened, and unshielded 802.5/Token Ring networks at transfer rates of 4 Mb/s or 16 Mb/s. The following modules are available for use in the DEChub platforms.
PAGE 137
3.11 Token Ring 3.11.1 DECmau 900TH The DECmau 900TH is an intelligent Token Ring Multistation Access Unit (MAU) that is fully compatible with the IEEE 802.5 standard and IBM Token Ring environments. The module is designed to support both 4 MB/s and 16 MB/s ring speeds, and provides 24 lobe ports for a star-wired topology. It accommodates 100-ohm shielded twisted-pair and unshielded-twisted-pair cabling using shielded 8-pin MJ connectors and IBM-type data connectors using BN26T cable adapters.
PAGE 138
3.11 Token Ring Protocol 802.5 Token Ring Media Twenty four 8-pin MJ ports, 100-ohm unshielded twisted-pair or shielded twistedpair cable. Use a balun (BN26T) for connection to 150 ohm shielded twisted-pair. LAN Connectivity Connects to either Token Ring 1 or 2. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the integral hub management agent. • DEChub 90—Not installable.
PAGE 139
3.11 Token Ring • Installs in any token ring network, supporting 4 MB/s or 16 MB/s speeds. • Eliminates recabling by accepting 100-ohm UTP or STP cable using 8-pin MJ and IBM type data connectors using BN26T cable adapters. • Ensures reliable connections by repeating and retiming the signal.
PAGE 140
3.11 Token Ring 3.11.2 DECswitch 900ET The DECswitch 900ET interconnects two Token Ring LANs to an Ethernet LAN. The module is designed to support both 4 MB/s and 16 MB/s ring speeds over 100ohm shielded twisted- pair and unshielded-twisted-pair cabling using shielded 8-pin MJ connectors and IBM-type data connectors. For Ethernet LANs, both the AUI and 10BaseT can be directly connected to the module. 10Base2 is supported via an external adapter.
PAGE 141
3.11 Token Ring Media Two 8-pin MJ ports, 100-ohm unshielded twisted-pair or shielded twisted-pair cable. Use a balun (BN26T) for connection to 150 ohm shielded twisted-pair. One 8-pin MJ port (10BaseT). and one AUI. LAN Connectivity • Connects to either Token Ring 1 or 2 in a DEChub 900 MultiSwitch. • Connects through the AUI in the DEChub ONE. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable.
PAGE 142
3.11 Token Ring Features • Installs in any token ring network, supporting 4 MB/s or 16 MB/s speeds. • Eliminates recabling by accepting 100-ohm UTP or STP cable using 8-pin MJ and IBM type data connectors using BN26T cable adapters.
PAGE 143
3.11 Token Ring 3.11.3 DECrepeater 900SL The DECrepeater 900SL is a ring-in/ring-out repeater module, that is used to provide connection to the 802.5 Token Ring trunk wiring. The repeater is configured with two 150-ohm DB9 connections over 150-ohm shielded twisted-pair cable. The repeater allows for extended distances of up to 300 meters. Figure 3–32 shows the DECrepeater 900SL network module. Figure 3–32 DECrepeater 900SL Platform This half-height module is used in the DEChub 900 MultiSwitch.
PAGE 144
3.11 Token Ring Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the integral hub management agent. • DEChub 90—Not installable. • DEChub ONE—Not installable. • DEChub ONE-MX—Not installable. • Standalone—Not installable. Supported MIBs • DEChub 900 Public Common MIB • DEChub 900 Token Ring Common MIB IP Service Not an IP Services provider.
PAGE 145
3.11 Token Ring 3.11.4 DECrepeater 900TL The DECrepeater 900TL is a ring in/ring out repeater module, that is used to provide connection to the 802.5 Token Ring trunk wiring. The repeater is configured with two 8-pin MJ ports and supports connections over 100-ohm unshielded twisted-pair (UTP) cable. The repeater allows for extended distances of up to 200 meters. Figure 3–33 shows the DECrepeater 900TL network module.
PAGE 146
3.11 Token Ring Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the integral hub management agent. • DEChub 90—Not installable. • DEChub ONE—Not installable. • DEChub ONE—Not installable. • Standalone—Not installable. Supported MIBs • DEChub 900 Public Common MIB • DEChub 900 Token Ring Common MIB • MIB II (RFC 1213) IP Service Not an IP Services provider.
PAGE 147
3.11 Token Ring 3.11.5 DECrepeater 900FL The DECrepeater 900FL is a ring-in/ring-out repeater module, that is used to provide connection to the 802.5 Token Ring trunk wiring. The repeater is configured with two ST type fiber-optic ports on the front panel and two RJ45 8-pin connectors (UTP) on the rear panel. Figure 3–34 shows the DECrepeater 900FL network module.
PAGE 148
3.11 Token Ring Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the integral hub management agent. • DEChub 90—Not installable. • DEChub ONE—Not installable. • DEChub ONE—Not installable. • Standalone—Managed through the built in SNMP agent.
PAGE 149
3.12 Probes 3.12 Probes Packet probe modules act as distributed network monitoring performance devices. They implement the Simplified Network Monitoring Protocol (SNMP) Remote Monitoring (RMON) Management Information Base (MIB). Modules are available for Ethernet and Token Ring networks. The following modules are available for use in the DEChub platforms or as standalone devices. • • DECpacketprobe 90 DECpacketprobe 900RR 3.12.
PAGE 150
3.12 Probes Platform This half-height module is used in the: • Digital MultiStack System • DEChub 900 MultiSwitch • DEChub 90. • When used standalone it requires a separate power unit. Protocol Ethernet 802.3 Media One 8-pin MJ connection. LAN Connectivity • One ThinWire BNC when installed in the Digital MultiStack System. • One backplane ThinWire when installed in a DEChub 900 MultiSwitch. • One backplane ThinWire when installed in a DEChub 90. • One ThinWire BNC when standalone.
PAGE 151
3.12 Probes Supported MIBs • RMON • MIB II (RFC 1213) IP Service Not an IP Services provider.
PAGE 152
3.12 Probes 3.12.2 DECpacketprobe 900RR The DECpacketprobe 900RR operates as a distributed network performance monitoring probe. It is attached to the Token Ring network (4 MB/s or 16 MB/s) to monitor traffic and error levels. The module implements the Simplified Network Management Protocol (SNMP) Remote Monitoring (RMON) Management Information Base (MIB) for monitoring Ethernet LANs. Requires RMON Manager.
PAGE 153
3.12 Probes LAN Connectivity • Connects to Token Ring 1 or 2 when installed in a DEChub 900 MultiSwitch. Upgrade Method • Flash Loader • TFTP via the Setup port. Manageability • Digital MultiStack System—Not installable. • DEChub 900 MultiSwitch—Managed through the module’s built in SNMP agent. • DEChub 90—Not installable. • DEChub ONE—Not installable. • DEChub ONE-MX—Not installable. • Standalone—Not installable.
PAGE 154
PAGE 155
4 Management Methods This chapter describes the methods used to manage DEChub and Digital MultiStack Systems products. 4.1 Introduction Two methods are available for DEChub and Digital MultiStack System management: in-band management and out-of-band management. In-band management is the network based method that transports management requests over the LAN.
PAGE 156
4.2 In-Band Management A proxy agent is an IP addressable module that communicates in more than one protocol. It communicates with the network management station in its protocol (SNMP), and communicates in other protocols to other devices that cannot communicate directly with the network management station. The device acts as the “proxy” or interpreter between the network management station and these modules.
PAGE 157
4.2 In-Band Management 4.2.1 IP Services The DEChub 900 MultiSwitch Hub Manager cannot communicate with the network directly over the DEChub 900 MultiSwitch serial management bus. For it to communicate with the network it requires a module that can receive and transmit messages over the serial management bus. This is called an IP Services module. The combination of the IP address and IP Service Module at that assigned slot location establishes the primary In-band management path.
PAGE 158
4.
PAGE 159
4.2 In-Band Management Module IP Services DECserver 90M No DECserver 900TM Yes DECserver 900GM Yes Management Agents DECagent 90 No Token Ring DECmau 900TH No DECswitch 900ET No DECrepeater 900SL No DECrepeater 900TL No DECrepeater 900FL No Probes DECpacketprobe 90 No DECpacketprobe 900RR No 4.2.2 Digital MultiStack System In-Band Management To manage the Digital MultiStack System, install and designate a module as the stack manager (or proxy agent).
PAGE 160
4.2 In-Band Management 4.2.4 DEChub 900 MultiSwitch In-Band Management To manage the DEChub 900 MultiSwitch, install a module that provides IP services into the chassis. You then assign the In-Band IP address for the Hub Manager to the slot location containing the IP Services module. 4.2.5 DEChub ONE or DEChub ONE-MX In-Band Management You can directly manage modules that have their own built-in SNMP agent. Modules without integral agents require management by a proxy agent located somewhere on the LAN.
PAGE 161
4.3 Out-of-Band Management 4.3 Out-of-Band Management Out-of-band management (OBM) enables you to run any SNMP network management application using the Serial Line Internet Protocol (SLIP), directly at the platform or module without transport over the LAN. You can use out-of-band management to manage network modules installed in a platform that has a built-in OBM port. Additionally, many network modules have their own OBM port.
PAGE 162
4.3 Out-of-Band Management The out-of-band management options for standalone modules are: • • DEChub ONE or DEChub ONE-MX – Use the docking station’s OBM port. – Use the module’s OBM port. Standalone module – Use the module’s OBM port. 4.3.1 Digital MultiStack System Out-of-Band Management To manage the Digital MultiStack System, use the OBM port of the module acting as the stack manager. 4.3.
PAGE 163
5 Management Tools This chapter describes the software tools used to for managing products. 5.1 Introduction The DEChub and Digital MultiStack System products and standalone modules are manageable by any application software that supports native SNMP. Typically, the application software of choice is clearVISN. clearVISN is an integrated family of software applications for managing a network using policy-based techniques. clearVISN focuses on networking products.
PAGE 164
5.2 clearVISN Applications 5.2 clearVISN Applications The clearVISN applications are listed and described in Table 5–1. The sections following the table describe the applications in detail. Table 5–1 clearVISN Applications: 5–2 Application Name Purpose clearVISN Router Launches two applications: Router Configurator and Router Manager. clearVISN core functionality, for example, the TFTP Server, also resides here.
PAGE 165
5.2 clearVISN Applications Application Name Purpose RMON Manager Manages devices that support the Remote Monitoring (RMON) Management Information Base (MIB). RMON Manager uses SNMP to obtain the RMON MIB data from DECpacketprobes and Ethernet switches that have up to full nine group RMON code. It allows you to configure probes and view performance data. It also contains extensive protocol decoding capability.
PAGE 166
5.3 Router Configurator 5.3 Router Configurator The Router Configurator is a software application that enables you to create, modify and load configuration information for supported bridging routers. The Router Configurator has a Graphical User Interface (GUI). You configure individual bridging routers by entering information on tab pages (screens) for the various router features that you want.
PAGE 167
5.3 Router Configurator 5.3.2 Supported Devices You can use the Router Configurator to configure and load the following bridging routers: • RouteAbout Access EI • RouteAbout Access EW • RouteAbout Access TW • RouteAbout Central EI • RouteAbout Central EW • DECswitch 900 EE (with routing firmware) • DECswitch 900 EF (with routing firmware) • DECswitch 900 ET • DECswitch 900FO Note DECnis support will be added in the future.
PAGE 168
5.4 Router Manager 5.4 Router Manager The clearVISN Router Manager application is used for managing a routed network composed of routers from Digital Equipment Corporation, Cisco, Bay Networks, Novell and 3Com. It does this by working with the IETF standard Management Information Base (MIB), and the enterprise-specific extensions defined by these vendors for their router products. clearVISN Router Manager can also manage other routers and bridges in a limited fashion by working with their standard MIB.
PAGE 169
5.
PAGE 170
5.5 MultiChassis Manager 5.5 MultiChassis Manager MultiChassis Manager is a flexible, network configuration and management application that features a graphical user interface (GUI). MultiChassis Manager manages 90-series and 900-series network modules, in hubs or standalone, the DEChub 900 MultiSwitch, the GIGAswitch/FDDI system, and the GIGAswitch/ ATM system.
PAGE 171
5.
PAGE 172
5.6 Stack Manager 5.6 Stack Manager Stack Manager is a flexible, network configuration and management application that features a graphical user interface (GUI). Stack Manager manages 90-series network modules, standalone, in a DEChub 90, or in the Digital MultiStack System. To communicate configuration and management commands to network modules, Stack Manager sends Simple Network Management Protocol (SNMP) commands to SNMP management agents in the network modules or in the hub itself. 5.6.
PAGE 173
5.7 VLAN Manager 5.7 VLAN Manager VLAN Manager is a clearVISN application that runs on the Windows 95 or Windows NT operating system. It enables you to logically segment your network into virtual LANs (VLANs). A virtual LAN is a broadcast domain whose membership is based on logical groupings instead of physical media connections. This means that LAN membership can be defined by users’ communication needs to rather than the physical connections of nodes and media.
PAGE 174
5.7 VLAN Manager VLAN Manager also enables you to configure more secure networks because each VLAN is a separate broadcast domain that defines which devices and users receive the broadcast packets. 5.7.1 VLAN Manager Benefits VLAN Manager enables you to optimize performance, ensure proper levels of security, and dynamically adapt to network changes.
PAGE 175
5.7 VLAN Manager 5.7.2 VLAN Manager Features Specific features of VLAN Manager are as follows: • Provides a project-group oriented NMS to configure VLANs on switched networks based on Digital’s switching products. • Operates independently or in conjunction with other network management applications on a common clearVISN management platform. • Includes a graphical user interface (GUI) that is user-friendly and that simplifies the management of network switching devices.
PAGE 176
5.8 Flash Loader 5.8 Flash Loader The Flash Loader application allows you to perform firmware upgrades on hubs, hub modules, and the GIGAswitch/FDDI system. The device to be loaded is referred to as the agent. 5.8.
PAGE 177
5.9 Recovery Manager 5.9 Recovery Manager The Recovery Manager application is used to save the configuration of a supported network device to a file on disk and restore that configuration back to the network device. The graphical user interface allows you to restore the configuration settings to the same or to a like module. You can back up and restore an entire hub configuration or a partial hub configuration. 5.9.
PAGE 178
5.9 Recovery Manager 5.9.3 Partial Configuration Partial backups and restores provide more flexibility and control over networks than do backups and restores of entire hubs. Partial configurations include backups and restores of the following: • Individual slots or groups of slots A device failure is an example of when to execute a partial configuration — in this case, to restore saved parameters to the replacement device.
PAGE 179
5.
PAGE 180
5.10 RMON Manager 5.10 RMON Manager RMON Manager is an application for managing devices that support RFC 1757 and RFC 1513, the Remote Network Monitoring Management Information Base (MIB) for Ethernet and Token Ring, respectively. RMON Manager gathers a wide variety of statistical information about network operation by examining each packet passed on a network segment. Segment statistics are stored in counters within the agent (often called a probe).
PAGE 181
5.10 RMON Manager 5.10.
PAGE 182
PAGE 183
6 Configuration Examples This chapter contains a series of configuration examples. 6.1 Introduction These configurations are samples of small to moderate sized networks designed using DEChub products: • Case 1 - Managed 10BaseT Workgroup. • Case 2 - Small Mixed Media Ethernet Workgroup. • Case 3 - Multi-Ethernet Hub. • Case 4 - Multi-Ethernet (Building) Backbone. • Case 5- Collapsed Fiber Optic (Campus) Ethernet Backbone. • Case 6- Shared FDDI Backbone. • Case 7- Switched FDDI Backbone.
PAGE 184
6.2 Case 1: Managed 10BaseT Workgroup 6.2 Case 1: Managed 10BaseT Workgroup Goal Design and build a simple workgroup supporting personal computers, servers, and printers in a limited area. The work group is supported by a single fiber optic cable segment from a central site. Design Requirements • Thirty-two ports of 10BaseT desktop or server connectivity. • Device wiring is Unshielded Twisted Pair (UTP). • Backbone connection is 10BaseFL (fiber optic). • Network management.
PAGE 185
6.
PAGE 186
6.3 Case 2: Small Mixed Media Ethernet Workgroup 6.3 Case 2: Small Mixed Media Ethernet Workgroup Goal Develop a small managed workgroup environment that supports a mixture of personal computers, workstations, and terminals. The workgroup is one of a series of workgroups off a distributed backbone. The workgroup is located on one floor of a multifloor building and uses a single Ethernet fiber optic cable as the backbone connection.
PAGE 187
6.
PAGE 188
6.4 Case 3: Multi-Ethernet Hub 6.4 Case 3: Multi-Ethernet Hub Goal Provide a collapsed backbone hub to support five separate LANs. Design Requirements • Collapsed backbone hub. • Four redundant Ethernet fiber connections to remote LANs. • Local Ethernet LAN with: – Eight 10BaseT ports – Thirty-two asynchronous ports – Six 10Base2 (ThinWire) ports – A Brouter with T1 WAN connection • Full speed bridge support between all five LANs. • Network management.
PAGE 189
6.4 Case 3: Multi-Ethernet Hub Once the hardware has been installed, the clearVISN MultiChassis Manager software is used to configure the hub and the modules. Options The extra port on the DECswitch 900EE could be used to provide a separate LAN for connection to: • • • A central server. The DECserver 900TM. The DECbrouter 90T1. You can substitute the DECrepeater 90T16 with the DECrepeater 900TM or PORTswitch 900TP for higher density and/or more management and configuration control.
PAGE 190
6.4 Case 3: Multi-Ethernet Hub All connections between the modules are made under software control using clearVISN MultiChassis Manager. Figure 6–4 shows MultiChassis Manager’s LAN interconnect window for the hub.
PAGE 191
6.5 Case 4: Multi-Ethernet (Building) Backbone 6.5 Case 4: Multi-Ethernet (Building) Backbone Goal Design a multi-Ethernet building network. The network is in a multifloor building and supports several departments. Design Requirements • Build LANs with WAN access. • A centralized department is located on its own floor in the building, with shared services and bridging between all LANs in the building. • Four different departments, each located in separate floors of the same building.
PAGE 192
6.5 Case 4: Multi-Ethernet (Building) Backbone – DECrepeater 90FA – DECagent 90 – DECserver 90TL – DECrepeater 90T16 (two) – DECrepeater 90C Suggested Configuration - Department 2: This configuration is similar to Case 1. • Platform type: DEChub ONE • Network Module: – DECrepeater 900TM Suggested Configuration - Department 3: This configuration is similar to Case 2.
PAGE 193
6.
PAGE 194
6.5 Case 4: Multi-Ethernet (Building) Backbone All connections between the modules are made under software control using clearVISN MultiChassis Manager. Figure 6–6 shows MultiChassis Manager’s LAN interconnect window for the central department.
PAGE 195
6.5 Case 4: Multi-Ethernet (Building) Backbone Figure 6–7 shows MultiChassis Manager’s LAN interconnect window for Department 4.
PAGE 196
6.6 Case 5: Collapsed Fiber Optic (Campus) Ethernet Backbone 6.6 Case 5: Collapsed Fiber Optic (Campus) Ethernet Backbone Goal Design a collapsed fiber optic campus backbone. This is similar to Case 4, but there is no fiber optic redundancy, allowing the use of a DECswitch 900FO. Groups are spread across multiple buildings. FDDI shared backbone is a likely future migration.
PAGE 197
6.6 Case 5: Collapsed Fiber Optic (Campus) Ethernet Backbone – DECserver 90TL – DECrepeater 90T16 (two) – DECrepeater 90C Suggested Configuration - Building 2: This configuration is similar to Case 1. • Platform type: DEChub ONE • Network Module: – DECrepeater 900TM Suggested Configuration - Building 3 (Multi-LAN Building): • Platform type: DEChub 900 MultiSwitch • Network Modules: – PORTswitch 900FP – PORTswitch 900TP (three). These allow load balancing of 96 users across 3 LANs.
PAGE 198
6.
PAGE 199
6.6 Case 5: Collapsed Fiber Optic (Campus) Ethernet Backbone All connections between the modules are made under software control using clearVISN MultiChassis Manager. Figure 6–9 shows MultiChassis Manager’s LAN interconnect window for the central department.
PAGE 200
6.6 Case 5: Collapsed Fiber Optic (Campus) Ethernet Backbone All connections between the modules are made under software control using clearVISN MultiChassis Manager. Figure 6–10 shows MultiChassis Manager’s LAN interconnect window for building 3.
PAGE 201
6.7 Case 6: Shared FDDI Backbone 6.7 Case 6: Shared FDDI Backbone Goal Migrate to a larger network with a shared dual FDDI Backbone. Design Requirements • Migration of the local shared workgroups of up to 192 users to higher bandwidth. • Provide FDDI shared network servers. • Have network management. Suggested Configuration • Platform types: – • • DEChub 900 MultiSwitch (three) Network Modules: – DECswitch 900EF – DECconcentrator 900MX.
PAGE 202
6.
PAGE 203
6.7 Case 6: Shared FDDI Backbone All connections between the modules are made under software control using clearVISN MultiChassis Manager. Figure 6–12 shows MultiChassis Manager’s LAN interconnect window for the workgroup concentrators.
PAGE 204
6.8 Case 7: Switched FDDI Backbone 6.8 Case 7: Switched FDDI Backbone Goal Migrate a large shared FDDI backbone to switched FDDI backbone. Design Requirements • Migration of the local workgroups to higher bandwidth. • Provide shared network servers. • Have network management.
PAGE 205
6.
PAGE 206
6.8 Case 7: Switched FDDI Backbone All connections between the modules are made under software control using clearVISN MultiChassis Manager. Figure 6–14 shows MultiChassis Manager’s LAN interconnect window for the workgroup hubs.
PAGE 207
6.9 Case 8: Remote Access Using Routers and Access Servers 6.9 Case 8: Remote Access Using Routers and Access Servers Goal Provide personal computer and terminal users with connectivity flexibility. Typically users will require both local and remote access to the office and remote access to a central corporate site. Design Requirements • Support a single multiprotocol Ethernet LAN • Have network management. Suggested Configuration Figure 6–15 shows the sample configuration.
PAGE 208
6.
PAGE 209
6.10 Case 9: Connecting Remote Sites to a Cisco Backbone 6.10 Case 9: Connecting Remote Sites to a Cisco Backbone Goal Connect remote sites to the existing Cisco backbone. Design Requirements • Remote sites need access to existing network with a Cisco backbone. • Sites use a variety of both routable and non-routable protocols • Network management. Suggested Configuration Figure 6–16 shows the sample configuration.
PAGE 210
6.
PAGE 211
A FDDI Configuration Capabilities This appendix describes FDDI configuration capabilities that are supported in DEChub 900 FDDI network modules. The descriptions discussed in this appendix assume that the reader is familiar with basic FDDI configuration rules and understands the differences between an A, B, M, and S port. If these terms are not familiar to you, refer to Appendix B in this manual for an overview of FDDI concepts that are discussed in this appendix.
PAGE 212
A.1 Configuration Guidelines and Rules A.1 Configuration Guidelines and Rules This section details the configuration capabilities that are supported in the DEChub 900 family of FDDI products. A.1.1 Individual FDDI Networks Individual FDDI networks can be configured as either a dual ring or a tree. This allows compliancy with FDDI configuration rules which operate at the module level and are independent of MultiChassis Manager. A.1.
PAGE 213
A.1 Configuration Guidelines and Rules A.1.5 DEChub 900 Backplane Technically, any type of configuration (dual ring, tree, or dual ring of trees) can be created in the DEChub 900 backplane; however, for ease of use, only dual ring and tree configurations are supported. Up to four independent FDDI networks can be created across the DEChub 900 backplane. Each of the created FDDI networks can be either a dual ring or a tree on the backplane, but not a mixture of both.
PAGE 214
A.2 Dual Ring Configurations A.2 Dual Ring Configurations DEChub 900 FDDI network modules support front panel as well as backplane FDDI ports. When configured in a dual ring topology, ports are assigned a ring port (A port or B port) by management. MultiChassis Manager users can assign a ring port using the Station Configuration window. Any SNMP based management software can also be used.
PAGE 215
A.3 Tree Configurations A.3 Tree Configurations When connected in a tree configuration, front panel ports and backplane ports are assigned a tree port (M port or S port) by management. MultiChassis Manager users can assign a tree port using the Station Configuration window. Any SNMP based management software can be used. A.3.1 Tree Port Configuration Examples Figure A–2 shows the tree port configurations that can be management assigned.
PAGE 216
A.4 DECconcentrator 900MX A.4 DECconcentrator 900MX The DECconcentrator 900MX is an eight-port FDDI concentrator (six front panel ports and two backplane ports). The two backplane ports (see Figure A–3) attach to a DEChub 900 MultiSwitch backplane or to a DEChub ONE-MX docking station that supports ModPMDs. A.4.1 Port Assignments Port 1 can be configured as either an A or M port and Port 6 can be configured as either a B, S, or M port. Ports 2 to 5 are always M ports.
PAGE 217
A.5 DECconcentrator 900TH A.5 DECconcentrator 900TH The DECconcentrator 900TH is a sixteen port FDDI concentrator (fourteen front panel ports and two backplane ports). The two backplane ports, see Figure A–4, attach to a DEChub 900 MultiSwitch backplane or to a DEChub ONE-MX docking station that supports ModPMDs. Twelve of the front panel ports are fixed unshielded twisted pair (UTP) connections.
PAGE 218
A.6 DECconcentrator 900FH A.6 DECconcentrator 900FH The DECconcentrator 900FH is a sixteen port FDDI concentrator (fourteen front panel ports and two backplane ports). The two backplane ports, see Figure A–5, attach to a DEChub 900 MultiSwitch backplane or to a DEChub ONE-MX docking station that supports ModPMDs. Twelve of the front panel ports are fixed multimode fiber (MMF), SC optics connections.
PAGE 219
A.7 DECswitch 900EF A.7 DECswitch 900EF The DECswitch 900EF (previously called the DECbridge 900MX) supports two FDDI ports that can be individually assigned to either the module’s front panel (Port 1A/M and Port 1B/S) or to the backplane ports for connection to a DEChub 900 MultiSwitch or to a DEChub ONE-MX docking station.
PAGE 220
A.8 PEswitch 900TX A.8 PEswitch 900TX Unlike the DECswitch 900EF module, the PEswitch 900TX module supports two FDDI port connections to the DEChub 900 MultiSwitch backplane or to the DEChub ONE-MX docking station only. There are no front panel FDDI ports on the PEswitch 900TX module. A.8.1 Port Assignments The FDDI port assignments are software configurable via MultiChassis Manager or the set up port menu.
PAGE 221
A.9 FDDI in the Hub Backplane A.9 FDDI in the Hub Backplane The DEChub 900 MultiSwitch and the DEChub ONE-MX use a building block approach for configuring FDDI on the backplane. The network manager assigns a port type by selecting a building block. A.9.1 FDDI Building Blocks Building blocks are divided into two groups: • Ring Building Blocks • Tree Building Blocks There are nine building blocks; four are used for building dual rings, and five are used for building trees.
PAGE 222
A.9 FDDI in the Hub Backplane Figure A–8 Ring Building Blocks Front Panel Ports A B Trunk B Trunk AB B A B Trunk A A B Stump Primary A Backplane Ports LKG-10070-96F A.9.3 Tree Building Blocks The five tree building blocks, see Figure A–9, are as follows: Name Description Nonroot MS Ports M and S connect to the DEChub 900 backplane or to the DEChub ONE-MX ModPMDs. Nonroot M Port M connects to the DEChub 900 backplane or to the DEChub ONE-MX ModPMD.
PAGE 223
A.
PAGE 224
A.10 Default Configurations A.10 Default Configurations This section describes the default (or factory set) configurations that apply to the FDDI network modules. Note that the default settings vary according to module type, and whether the module is installed into a DEChub 900 MultiSwitch, DEChub ONE or DEChub ONE-MX docking station. A.10.
PAGE 225
A.10 Default Configurations NOTE The DEChub ONE (DEHUA) supports one Ethernet connection, and the DEChub ONE-MX (DEF1H) supports one Ethernet connection and up to two ModPMD FDDI connections. A.10.3 Enabling ModPMD Ports To use the ModPMD ports of the DEChub ONE-MX a network manager must issue the appropriate MultiChassis Manager commands to enable the ModPMD ports, using the building blocks previously described.
PAGE 226
A.10 Default Configurations A.10.6 Example of Module Reacting to Change of Environment If a DECswitch 900EF module, that is configured with an S port and M port on the ModPMDs, is moved from a DEChub ONE-MX docking station to another, the module powers up with the ModPMDs of the second DEChub ONE-MX enabled as S and M ports (previous configuration recall ability).
PAGE 227
A.11 FDDI Tree Configuration Examples A.11 FDDI Tree Configuration Examples The DEChub 900 backplane supports many types of FDDI tree configurations. FDDI trees can be contained within the hub backplane and can connect an individual tree in the hub backplane to a higher level of a tree, or can be used to interconnect other hubs.
PAGE 228
A.11 FDDI Tree Configuration Examples Figure A–10 DECconcentrator Tree Connections in Hub Backplane Front Panel Ports M M M M M M M M M M M M M M M M M M Concentrator 1 Concentrator 2 Concentrator 3 M M M S S S Backplane Ports LKG-10074-96F Figure A–11 shows the building block representation of the configuration example described in Figure A–10.
PAGE 229
A.11 FDDI Tree Configuration Examples A.11.2 Example 2 — Self-contained Tree of Switches and Concentrators in Hub Backplane In this example (see Figure A–12), an FDDI tree is constructed entirely within the hub backplane; however, a mixture of FDDI network module types (switches and concentrators) is used. The backplane ports of the FDDI network modules are enabled as M ports and S ports.
PAGE 230
A.11 FDDI Tree Configuration Examples Figure A–13 Building Block Representation of Example 2 Non Root MS M Non Root MS S M Non Root MS S M S LKG-10077-96F A.11.3 Example 3 — Tree Connections to an External Concentrator FDDI trees that are constructed within the hub backplane can connect to an external higher level concentrator by configuring one of the FDDI network modules with a front panel S port, and configuring all other FDDI network modules with backplane M and S ports.
PAGE 231
A.11 FDDI Tree Configuration Examples Figure A–14 Tree Connections to an External FDDI Network Front Panel Ports PEswitch 900TX M S PEswitch 900TX M S DECswitch 900EF S M Backplane Ports LKG-10078-96F Figure A–15 shows the building block representation of the configuration example described in Figure A–14.
PAGE 232
A.11 FDDI Tree Configuration Examples A.11.4 Example 4 — Dual Homing and Connection to an External Dual Ring In some cases it is desirable to connect the hub to an external dual ring, and configure the network modules as FDDI trees within the hub backplane. In other cases, it is also desirable to have a redundant connection from the hub to higher level concentrators. This second case (see Figure A–16) is commonly referred to as dual homing.
PAGE 233
A.11 FDDI Tree Configuration Examples Figure A–17 Building Block Representation of Example 4 A Non Root MS M Non Root MS S M B Root Primary S M LKG-10081-96F A.11.5 Example 5 — FDDI Tree Extensions You can configure an FDDI network module, that is at the end of a branch of an FDDI tree, with front panel M ports. The M port can then be used to connect to an external FDDI network module or to an additional hub (see Figure A–18).
PAGE 234
A.11 FDDI Tree Configuration Examples Figure A–18 Hub-Based Tree Connections to an External FDDI Network Front Panel Port DEChub 900 S FDDI Station M S DECswitch 900EF M S DECswitch 900EF M External Module Backplane Port LKG-10082-96F Figure A–19 shows the building block representation of the configuration example described in Figure A–18.
PAGE 235
A.12 Dual Ring Configuration Examples A.12 Dual Ring Configuration Examples Both dual rings and trees are supported across the DEChub 900 MultiSwitch backplane. However, because it has more robust and quicker fault tolerance capabilities than tree configurations, the dual ring configuration is more effective to use across the backplane.
PAGE 236
A.12 Dual Ring Configuration Examples Figure A–20 DECconcentrator Dual Ring Connected to an FDDI Network Front Panel Ports A M M M M M M M M M M M M M M M M B Concentrator 1 Concentrator 2 Concentrator 3 A A B B Backplane Ports LKG-10084-96F Figure A–21 shows the building block representation of the configuration example described in Figure A–20.
PAGE 237
A.12 Dual Ring Configuration Examples A.12.2 Example 2 — Dual Ring Switches Connected to an External Dual Ring As shown in Figure A–22, all of the DECswitch 900EF modules (Switches 1 through 3) can connect directly to the dual ring for this dual ring configuration (similar to the concentrators shown in Example 1). Switch 3 has its B port assigned to the front panel port connection and the A port assigned to the backplane port connection.
PAGE 238
A.12 Dual Ring Configuration Examples Figure A–23 Building Block Representation of Example 2 A B Trunk B Trunk AB B A Trunk A B A LKG-10087-96F A.12.3 Example 3 — PEswitch 900TX Connections to External Dual Ring The PEswitch 900TX module can be configured into a dual ring, however, because the module does not have front panel FDDI port connectors, two DECswitch 900EF modules or two DECconcentrator modules (in any combination) are required to complete the connection to an external FDDI network.
PAGE 239
A.12 Dual Ring Configuration Examples Figure A–24 Dual Ring Connections for PEswitch 900TX Front Panel Ports A M M M M M B DECswitch 900EF B PEswitch 900TX A B DECconcentrator 900TH A Backplane ports LKG-10088-96F Figure A–25 shows the Building block representation of the configuration example described in Figure A–24.
PAGE 240
A.12 Dual Ring Configuration Examples A.12.4 Example 4 — Self Contained Dual Ring in the Backplane You can create a dual ring, that is completely contained in the DEChub 900 backplane, by connecting all the backplane ports of the FDDI network modules together (see Figure A–26. Note that the DECconcentrator in Figure A–26 is providing M port tree connections to externally treed FDDI stations (such as, bridges, concentrators or end user stations that use S, A, or B ports).
PAGE 241
A.13 Fault Tolerance in Dual Rings A.13 Fault Tolerance in Dual Rings This section describes the fault tolerant safeguards that are built into DEChub 900 network modules. A.13.1 Maintaining Network Connectivity When a concentrator or switch in a dual ring is removed (hot swapped), the FDDI ring wraps according to FDDI standards.
PAGE 242
A.13 Fault Tolerance in Dual Rings If, at a later time, a replacement concentrator of the same type is installed into the same slot that held Concentrator 2, the replacement concentrator will be reinserted into the ring through the Auto Healing feature.
PAGE 243
A.14 Fault Tolerance in Trees A.14 Fault Tolerance in Trees This section describes the fault tolerant safeguards (for trees) that are built into DEChub 900 network modules. A.14.1 Maintaining Network Connectivity When a concentrator or switch in a tree is removed (hot swapped), the FDDI tree splits into two independent networks, per the FDDI standard.
PAGE 244
A.14 Fault Tolerance in Trees A.14.2 Example of Tree Backplane Healing As shown in Figure A–28, if Concentrator 1 is removed, Concentrator 2 and Switch 1 continue communications with each other and with all other FDDI stations in the tree. If Concentrator 2 fails, Concentrator 1 and Switch 1 can no longer communicate with each other. Within seconds of when Concentrator 2 becomes unavailable, the Hub Manager automatically reconnects Switch 1 to Concentrator 1 and the tree is reestablished.
PAGE 245
A.15 Token Ordering of Trees or Dual Rings A.15 Token Ordering of Trees or Dual Rings The DEChub 900 backplane uses a defined token order algorithm for FDDI dual rings or trees that are created in the hub. This section describes how the algorithm controls the token flow in the DEChub 900 backplane. A.15.1 Description The token flow is defined as the order in which the token flows to the MAC addressed slots in the DEChub 900 backplane.
PAGE 246
A.15 Token Ordering of Trees or Dual Rings Figure A–29 Token Flow through Dual Ringed DEChub 900 Modules Secondary Primary A B A B AB AB 2 3 AB A B Slot 1 4 5 6 7 8 Token order on ring map = 4>1>2>3>6>8 = Location of MAC LKG-10072-96F Note that the front panel A port is shown on the module in slot 4, and the B port is shown on the module in slot 8. Therefore, the token, which is flowing on the primary ring, enters the hub at slot 4 and exits from slot 8.
PAGE 247
A.15 Token Ordering of Trees or Dual Rings A.15.3 Example 2 — Token Flow Through Treed Network Modules Figure A–30 shows the same hub that is now configured into a tree configuration with FDDI network modules in slots 1, 2, 3, 4, 6, and 8.
PAGE 248
A.16 Quick PC Trace Option for Concentrators A.16 Quick PC Trace Option for Concentrators A Quick PC Trace option is supported for all DEChub FDDI concentrator modules. A.16.1 PC Trace Description As defined by the FDDI standard, PC Trace is a method for recovering from a stuck beacon condition. All stations that are in the fault domain perform some level of hardware diagnostic test before attempting to reenter the FDDI network. Normally, concentrator modules run their full set of hardware diagnostics.
PAGE 249
A.17 Summary of Important Configuration Features A.17 Summary of Important Configuration Features This section reviews the FDDI configuration features for the DEChub 900 FDDI network modules. A.17.1 Support for Dual Ring and Tree Connections All DEChub FDDI modules support dual ring connections (A and B ports) and tree connections (M and S ports) across the DEChub 900 MultiSwitch backplane, or out of the front panel of individual FDDI network modules that are configured into a DEChub 900 MultiSwitch.
PAGE 250
A.17 Summary of Important Configuration Features A.17.5 Dual Ring of Trees Topology DEChub 900s can participate in a dual ring of trees topology as either part of the dual ring or as part of the tree. For example, a dual ring of trees can be constructed by first building a dual ring, then a tree, and connecting them together with a cable on the front panel (see Figure A–31).
PAGE 251
A.17 Summary of Important Configuration Features Figure A–32 Illegal Dual Ring of Trees Topology Front Panel Ports A B B A M S M S M Backplane ports LKG-10089-96F A.17.6 Dual Homing Dual-homing to multiple FDDI modules in a DEChub 900 can be supported in two ways: • Each module can be individually dual-homed via its front panel ports (assuming the module has front panel ports) • One concentrator module can be dual-homed and the other FDDI modules can be treed off that concentrator A.17.
PAGE 252
A.17 Summary of Important Configuration Features A.17.9 Self-Contained Tree Configuration You can build a self-contained tree configuration in the DEChub 900 with eight FDDI modules. This configuration can be built because it requires only 14 backplane channels. A.17.
PAGE 253
A.
PAGE 254
PAGE 255
B.1 The Dual Ring B FDDI Overview Fiber Distributed Data Interface (FDDI) is a set of ANSI/ISO standards for a 100 Mbps token passing ring which uses Multimode fiber, Single mode fiber, Unshielded Twisted Pair, Screened/Shielded Twisted Pair or any combination of the four as the transmission medium. This Appendix provides an overview of the applicable FDDI standards that govern the use of FDDI network modules. B.
PAGE 256
B.1 The Dual Ring All FDDI networks operate as logical token rings, where the right to transmit is granted by the possession of a token. There is one token per ring, and it is passed from station to station, according to a set of rules known as the timed token protocol. A station wishing to transmit on the ring first captures the token. It then transmits frames for a period of time determined by the timed token rules, and then releases the token immediately after completing its transmission.
PAGE 257
B.2 Station Types B.2 Station Types B.2.1 FDDI Network Building Blocks As shown in Figure B–2, FDDI networks are constructed using the following two types of devices: • Stations — there are two types of stations: Dual Attachment Stations (DAS) and Single Attachment Stations (SAS). • Concentrators — there are two types of concentrators: Dual Attachment Concentrators (DAC) and Single Attachment Concentrators (SAC).
PAGE 258
B.2 Station Types B.2.2 Dual Attachment Stations Dual Attachment Stations (DAS) attach directly to the dual ring. B.2.3 Single Attachment Stations Single Attachment stations connect to the ring via a concentrator, that can be of two types: • Dual Attachment Concentrator (DAC) — attaches directly to the dual ring • Single Attachment Concentrator (SAC) — attaches to the ring through other concentrators. B.2.
PAGE 259
B.3 Media Types and Maximum Distances B.3 Media Types and Maximum Distances B.3.1 Important Characteristics FDDI allows links to be built from the following media types. Fiber Media Fiber Type (Microns) Power Budget (Decibels) Maximum Link Distance (Kilometers) Multimode Fiber (MMF) 62.5/125 11 2.
PAGE 260
B.4 Station Configurations B.4 Station Configurations B.4.1 Identifying Stations and Concentrators Stations and Concentrators (see Figure B–3) can be identified by the types of ports that they use to attach to other stations: • A and B Ports — Dual Attachment Stations have A and B ports for attachment to other stations in the dual ring, or to concentrator M ports. • M Port — All concentrators, (SAC or DAC), are identifiable by the presence of M ports.
PAGE 261
B.4 Station Configurations B.4.2 MAC Location The FDDI rules require that a station’s Media Access Control (MAC) be physically located immediately prior to the port where the token exits the station. For Dual Attachment devices this means that the MAC is immediately ahead of the B port; for Single Attachment devices it is immediately ahead of the S port.
PAGE 262
B.5 Physical Topologies B.5 Physical Topologies B.5.1 Topology Types Although all FDDI networks are logical rings, the following physical topology types can be created: • Dual Rings • Trees • Dual Ring of Trees B.5.2 Dual Ring Topologies Dual Ring topologies (as shown in Figure B–1) are created by connecting only Dual Attachment Stations. The A port of one DAS station connects to the B port of the next DAS station, forming a physical connection between the two stations.
PAGE 263
B.5 Physical Topologies B.5.3 Tree Topologies FDDI also allows for the creation of tree topologies. Tree topologies start with a stand-alone concentrator at the top of the tree. Stations (DAS or SAS) or other concentrators (DACs) connect to this concentrator, and branch out from the top of the tree. • How to Identify Trees The distinguishing feature of a tree topology is the connection to an M port.
PAGE 264
B.
PAGE 265
B.6 Station States B.6 Station States B.6.1 Definition The station state is defined by FDDI standards as: the internal configuration of the paths within the station. Stations can be in one of two states: the Through state or the Wrap state (see Figure B–5). For example, DAS or DAC stations that are in an (unwrapped) dual ring are in the Through state. If a station detects a failure, causing it to wrap the rings together, that station transitions to the Wrap state.
PAGE 266
B.7 FDDI Connection Rules B.7 FDDI Connection Rules B.7.1 Predictability FDDI connection rules can seem complex and sometimes confusing, however, once clarified and understood, one can easily see how the applied rules prevent the formation of non-useful topologies that can disrupt communications among stations in the ring. FDDI connection rules also ensure that the ring always converges to a predefined topology.
PAGE 267
B.7 FDDI Connection Rules B.7.2 How Rings are formed FDDI rings are formed by the completion of physical connections between pairs of ports. The ports signal various parameters that are necessary for the successful completion of the connections. When a port attempts to form a connection with another port, it indicates both its own port type, and whether it wishes to form a connection with the port type that it senses at the other end of the link. B.7.
PAGE 268
B.
PAGE 269
B.7 FDDI Connection Rules B.7.6 Summary of FDDI Connection Rules Table B–1 summarizes the FDDI connection rules.
PAGE 270
B.8 Ring Operation B.8 Ring Operation B.8.1 Overview FDDI rings operate according to the rules of the Timed Token Protocol. The operation of the ring can be divided into two states: • Ring Initialization State • Steady State Operation B.8.2 Ring Initialization State The FDDI ring is initialized by a process known as the claim token process, that is invoked whenever a station enters or exits the ring, or if a failure of the normal ring operation is detected.
PAGE 271
B.8 Ring Operation B.8.5 Steady State In the steady state, the token circulates around the ring. The time for a token to circle once around the ring without being used by anyone is known as the token latency. Stations that wish to transmit must capture the token, and can transmit as long as allowed by the token holding rules. All stations keep a timer called the valid transmission timer (TVX) which they use for timing valid activity on the ring.
PAGE 272
PAGE 273
C Accessing Online Information This appendix describes how to access these products’ online release notes, public MIBs, Digital’s private MIBs, firmware images, and requests for comments (RFCs). C.1 Network Product Business Web Site Further information on these network products and topics is available on Digital’s Network Product Business Web Site as well as its Bulletin Board System. Both systems maintain a common, rich set of up-to-date information on NPB’s products, technologies, and programs.
PAGE 274
C.2 Using Electronic Mail To use the mail service, follow these instructions: 1.Send a mail message to SERVICE@NIC.DDN.MIL. 2.In the SUBJECT field, request the type of service that you want followed by any needed arguments. Normally the message body is ignored, but if the SUBJECT field is empty, the first line of the message body is taken as the request. The following example shows the SUBJECT lines you use to obtain DDN NIC documents: HELP RFC 822 RFC INDEX RFC 1119.PS FYI 1 IETF 1IETF-DESCRIPTION.
PAGE 275
Glossary This glossary contains definitions for DEChub and MultiStack terms and acronyms used in this manual. 8-pin MJ connector A jack used for connecting a cable terminated with an 8-pin MJ-compatible (RJ45) plug. access server A module that allows a terminal to connect to a network node. active port A redundant repeater port over which communication is currently taking place. An active port is enabled and handles any communication between the connected repeater ports.
PAGE 276
alarms Conditions in a hub or a community that the alarms software monitors. The conditions are detected by polling a predetermined list of MIBs on each type of network module. When a MIB value changes, the alarms software generates an alarm. attachment unit interface (AUI) A 15-pin “D”-sub connector interface that allows stations to connect to the Ethernet\IEEE 802.3 network. authorized station An addressable node on a local area network (LAN) that is capable of transmitting, repeating, and receiving data.
PAGE 277
BootP A protocol that is used by a network node to determine the Internet Protocol (IP) address of its Ethernet interfaces used for network booting. bridge (or MAC Bridge) An intelligent, protocol-independent, store-and-forward device that operates as a Data Link layer relay. Used to connect similar or dissimilar local area networks (LANs). A collection of LANs connected by bridges is referred to as an Extended LAN. brouter A bridge with minimal routing capabilities.
PAGE 278
concentrator The FDDI concentrator is a physical layer repeating device that allows the attachment of multiple single attachment stations, dual attachment stations, or other concentrators to the FDDI network. DECnet Digital networking software that runs on nodes in both local-area and wide-area networks.
PAGE 279
Ethernet A network communications system developed and standardized by Digital, Intel, and Xerox, using baseband transmission, CSMA/CD access, and logical bus topology. This industry-standard protocol is specified by ISO 8802-3 ANSI/IEEE Standard 802.3. Ethernet station An addressable node on an Ethernet network capable of transmitting and receiving data. An Ethernet station must contain a MAC. failover The feature that causes a failed link to automatically reconfigure to a redundant or “backup” link.
PAGE 280
filtering Filtering allows you to prevent, on per-port basis, a bridge from forwarding frames specified by address or protocol. flex(ible) channel A technology independent high-bandwidth channel that can support FDDI, Ethernet, Token Ring, or other interconnection needs. The DEChub 90 has one flex channel.
PAGE 281
GET A Simple Network Management Protocol (SNMP) request in which the named instance is retrieved if the community string matches. If the community string does not match, an error is returned. half height module A six-sided enclosure measuring approximately 1.25 inches x 10.5 inches x 4.5 inches. This module is installable in the Digital MultiStack System, DEChub 90, or DEChub 900. hot swap To “hot swap” a component means to remove and replace it while the system is in operation.
PAGE 282
Internet Protocol (IP) forwarding The forwarding of IP packets between interfaces (ports) on a DECserver 90TL, 90M, or 900TM. Internet Protocol (IP) name A unique alphanumeric string that identifies a device on the Internet. LAN See local area network (LAN). LAT See local area transport (LAT). LAN segment A portion of the LAN of a single media type, that is organized in a bus, a ring, or a point-to-point configuration.
PAGE 283
management agent See SNMP agent. management information base A dynamic, virtual collection of data about a managed object. The managed object provides this data to the network management station (NMS) which gathers the values from the managed object and loads them into the MIB representing the object. master mode A pair of repeater ports (primary and secondary) that control a redundant link.
PAGE 284
multiswitch backplane A backplane that allows flexible allocation of its signals so that multiple local area network (LAN) segments can be managed. The DEChub 900 MultiSwitch has a multiswitch backplane. network A collection of computer access terminals, and other devices together with the hardware and software that enables them to exchange data and share resources over either short or long distances.
PAGE 285
partition A repeater port is said to be partitioned when it is management disabled or autopartitioned. PC Personal computer. PHY A Fiber Distributed Data Interface (FDDI) standard that defines symbols, line states, clocking requirements, and the encoding of data for transmission. physical layer medium dependent FDDI standards that define the media and protocols to transfer symbols between adjacent PHYs. physical topology The arrangement of cables and hardware that make up the network.
PAGE 286
protocol filtering (MAC layer) A feature in some bridges that can be programmed to forward or reject transmissions that are originated under specified MAC protocols. proxy access The way a proxy Simple Network Management Protocol (SNMP) agent provides requests to the network management station (NMS). A proxy agent acts on behalf of network devices that do not support SNMP. When such a network module is to be managed, the NMS contacts the proxy agent and indicates the identity of the network module.
PAGE 287
responder port A redundant repeater port that connects to either a master primary or a secondary port. Because responder ports are always enabled, no action is taken to switch ports in case of link failure. However, a responder port does detect and report link failures to its partner (master primary or master secondary) port by continuously pulsing its fiber transmit LED on and off.
PAGE 288
session A logical connection between a terminal and a service node. SET A Simple Network Management Protocol (SNMP) request in which the named instance is modified if the community string matches. shielded twisted-pair A cable composed of two insulated wires, twisted together and surrounded by a braided metal shield or foil under the outer insulation. Simple Network Management Protocol (SNMP) A high-level, standards-based protocol for network management, usually used in TCP/IP networks.
PAGE 289
standalone module A network module in a single configuration such as a DEChub ONE. standby port A redundant repeater port that is configured as a backup port to an active port. A standby port is disabled and is held in readiness in case the active port fails. Telnet The TCP/IP standard protocol for remote terminal connections. Using Telnet, a user at one site can connect to a timesharing system at another site as if the user’s terminal is connected directly to the remote machine.
PAGE 290
PAGE 291
Index A Audience intended, ix B Backplane healing dual ring configurations, A-31 tree configurations, A-33 Beacon process, B-16 Book structure, x Bridge Modules half-height, 2-8 selecting, 2-8 Bridge Router Modules selecting, 2-12 Bridge Routers description, 3-59 Bridges description, 3-38 Brouter Modules selecting, 2-12 Brouters description, 3-59 Building blocks, FDDI, A-11 C Chaining, A-41 Cisco backbone connecting to, 6-27 Claim token process, B-16 clearVISN, 5-1 applications, 5-2 management applicati
PAGE 292
DECbridge 90 description, 3-39 IP service, 3-40 LAN connectivity, 3-40 manageability, 3-40 media, 3-40 platforms supported, 3-39 protocol, 3-40 supported MIBs, 3-40 upgrade method, 3-40 DECbridge 90FL description, 3-42 LAN connectivity, 3-43 manageability, 3-43 media, 3-43 platforms supported, 3-43 protocol, 3-43 supported MIBs, 3-43 upgrade method, 3-43 DECbrouter 90T1 description, 3-59 IP service, 3-61 LAN connectivity, 3-60 manageability, 3-61 media, 3-60 platforms supported, 3-60 protocol, 3-60 supporte
PAGE 293
description, 3-68 IP service, 3-70 LAN connectivity, 3-69 manageability, 3-69 media, 3-69 platforms supported, 3-69 port assignments, A-7 protocol, 3-69 supported MIBs, 3-70 upgrade method, 3-69 DEChub 90 description, 1-2 features, 1-2 in-band management, 4-2, 4-5 out-of-band management, 4-8 DEChub 900 backplane, A-3 description, 1-4 features, 1-6 in-band management, 4-2, 4-6 out-of-band management, 4-8 DEChub ONE change of environment, A-15 description, 1-9 in-band management, 4-2 power failure recovery, A
PAGE 294
protocol, 3-12 supported MIBs, 3-12 upgrade method, 3-12 DECrepeater 900SL description, 3-101 IP service, 3-102 LAN connectivity, 3-101 manageability, 3-102 media, 3-101 platforms supported, 3-101 protocol, 3-101 supported MIBs, 3-102 upgrade method, 3-102 DECrepeater 900TL description, 3-103 IP service, 3-104, 3-106 LAN connectivity, 3-103, 3-105 manageability, 3-104, 3-106 media, 3-103, 3-105 platforms supported, 3-103 protocol, 3-103 supported MIBs, 3-104, 3-106 upgrade method, 3-104, 3-106 DECrepeater 9
PAGE 295
IP service, 3-5 LAN connectivity, 3-5 manageability, 3-5 media, 3-5 platforms, 3-4 protocol, 3-4 supported MIBs, 3-5 upgrade method, 3-5 DECrepeater 90T-16 description, 3-6 IP Service, 3-7 LAN connectivity, 3-7 manageability, 3-7 media, 3-7 platform, 3-6 protocol, 3-6 supported MIBs, 3-7 upgrade method, 3-7 DECrepeater 90TS description, 3-8 IP service, 3-9 LAN connectivity, 3-9 manageability, 3-9 media, 3-9 platform, 3-8 protocol, 3-8 supported MIBs, 3-9 upgrade method, 3-9 DECrepeaters coaxial, 3-3 fiber,
PAGE 296
platforms supported, 3-76 protocol, 3-76 supported MIBs, 3-77 upgrade method, 3-76 DECswitch 900EE description, 3-49 IP service, 3-51 LAN connectivity, 3-50 manageability, 3-50 media, 3-50 platforms supported, 3-50 protocol, 3-50 supported MIBs, 3-51 upgrade method, 3-50 DECswitch 900EF, A-9 description, 3-52 IP service, 3-55, 3-58 LAN connectivity, 3-54, 3-57 manageability, 3-54, 3-57 media, 3-53, 3-57 platforms supported, 3-53, 3-57 port assignments, A-9 protocol, 3-53, 3-57 supported MIBs, 3-54, 3-58 upg
PAGE 297
ModPMD ports, A-15 Examples dual ring configuration, A-4 environment change reaction, A-16 FDDI tree configuration, A-17 tree configuration, A-5 F FDDI backplane channels, A-3 healing, A-31, A-33 beacon process, B-16 building blocks, A-11, B-3 chaining, A-41 claim token process, B-16 configuration features, A-39 guidelines and rules, A-2 connection rules, B-12 summary, B-15 DEChub 900 backplane, A-3 default configurations, A-14 dual attachment station, B-4 homed configuration, A-5 homing, A-22 ring and tre
PAGE 298
undesirable connections, B-13 valid configurations, A-42 Firmware loading, xii updates, xii Flash Loader, 5-14 features, 5-14 supported devices, 5-14 FTP, xii description, 3-74 Network Management Application Icons, 5-2 Network Modules types, 3-1 I PEswitch 900TX, A-10 description, 3-46 IP service, 3-48 LAN connectivity, 3-47 manageability, 3-47 media, 3-47 platforms supported, 3-47 port assignments, A-10 supported MIBs, 3-48 upgrade method, 3-47 Platform types, 1-1 Platforms, 1-1 selecting, 2-1 selection
PAGE 299
IP services, 3-33 LAN connectivity, 3-33 manageability, 3-33 media, 3-32 platform, 3-32 protocol, 3-32 supported MIBs, 3-33 upgrade method, 3-33 PORTswitch 900FP description, 3-35 IP service, 3-37 manageability, 3-36 media, 3-36 platforms supported, 3-35 protocol, 3-36 supported MIBs, 3-36 upgrade method, 3-36 PORTswitch 900TP description, 3-29 IP services, 3-30 LAN connectivity, 3-30 manageability, 3-30 media, 3-29 platforms supported, 3-29 protocol, 3-29 supported MIBs, 3-30 upgrade method, 3-30 PORTswitc
PAGE 300
Stack Manager, 5-10 features, 5-10 supported devices, 5-10 Stacking system, 1-7 features, 1-8 Station states, B-11 Switch Modules selecting, 2-9 Switches description, 3-45 T Token flow algorithm, A-35 ordering of trees or dual rings, A-35 Token Ring description, 3-94 Token Ring Modules selecting, 2-17 Tree topologies, B-9 advantage of, B-9 how to identify, B-9 U Updating firmware, xii V VLAN Manager, 5-11 benefits, 5-12 configuration flexibility, 5-12 features, 5-13 flexible access control, 5-12 performa