International Technical Support Organization 8260 Multiprotocol Intelligent Switching Hub May 1995 GG24-4370-00
IBML International Technical Support Organization 8260 Multiprotocol Intelligent Switching Hub May 1995 GG24-4370-00
Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xv. First Edition (May 1995) This edition applies to the 8260 Multiprotocol Intelligent Switching Hub family. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. An ITSO Technical Bulletin Evaluation Form for reader′s feedback appears facing Chapter 1.
Abstract This document describes the IBM 8260 Multiprotocol Intelligent Hub. It provides information about the 8260 architecture as well as how to install, configure and manage the 8260 Ethernet and token-ring media modules. This document was written for customers, systems engineers, network professionals and technical support personnel. Some knowledge of local area networks, token-ring and Ethernet architecture is assumed. (327 pages) Copyright IBM Corp.
iv 8260 Multiprotocol Intelligent Switching Hub
Contents Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Special Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How This Document is Organized . . . . . . . . . . . . . . . . . . . . . . Related Publications International Technical Support Organization Publications Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . .
4.4.1 Ethernet MAC Daughter Card (E-MAC) . . . . 4.4.2 Token-Ring MAC Daughter Card (T-MAC) . . . 4.5 Managing 8260 Using DMM and 8250 xMM 4.5.1 Managing 8260 with DMM . . . . . . . . . . . 4.5.2 Managing 8260 with 8250 xMM . . . . . . . . 4.6 Overview of Management and Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5.
8.4 Jitter Attenuator Daughter Card (JADC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5 Passive Port Technology . . . . . . . . . . . . . . . . . . . . . . . . 8.6 Active Port Technology . . . . . . . . . . 8.6.1 Per-Port Switching on the Active Modules 8.6.2 Static Switch on the Per-Port Switching Modules . . . . . . 8.7 Signal Flow on the 8260 Token-Ring Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.8 Speed Detection 8.8.
.6.3 SHOW COUNTER Command for Ethernet Networks . . . . . 10.6.4 Collecting and Displaying RMON Groups Using E-MAC . . . . . . 10.6.5 SHOW COUNTER Command for Token-Ring Networks 10.6.6 Collecting and Displaying RMON Groups Using T-MAC . . . . . . . . . . . . . . . . 10.7 Surrogate Functions Supported by T-MAC . . . . . . . . . . . . . . . 10.7.1 Using T-MAC Surrogate Functions 10.7.2 Displaying the Information Collected by Surrogate Features . . . . . . . . . . . . . . . . . . . 10.
Figures 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46. 47. 48. 49. 50. 51. Copyright IBM Corp. 1995 IBM 8260 Model 017 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Components of the 8250 Adapter Kit Enhanced TriChannel Bus . . . . . . . . . . . . . . . . . . . . . . . . . . 8260 ShuntBus . . . . . . . . . . . . . . . . . . . .
52. 53. 54. 55. 56. 57. 58. 59. 60. 61. 62. 63. 64. 65. 66. 67. 68. 69. 70. 71. 72. 73. 74. 75. 76. 77. 78. 79. 80. 81. 82. 83. 84. 85. 86. 87. 88. 89. 90. 91. 92. 93. 94. 95. 96. 97. 98. 99. 100. 101. 102. 103. 104. 105. x Installing 8260 Modules in an 8260 Not Managed by DMM . . . . . Installing 8250 Modules in an 8260 Managed by DMM . . . . . . . . . . . . . Installing 8250 Modules in an 8260 Not Managed by DMM Messages Received when a Power Failure Occurs . . . . . . . . . .
106. 107. 108. 109. 110. 111. 112. 113. 114. 115. 116. 117. 118. 119. 120. 121. 122. 123. 124. 125. 126. 127. 128. 129. 130. 131. 132. 133. 134. 135. 136. 137. 138. 139. 140. 141. 142. 143. 144. 145. 146. 147. 148. 149. 150. 151. 152. 153. 154. 155. 156. 157. 158. 159. 160. Trunk Wrapping in Active Per-Port Switching Module Trunk Wrapping in Active Per-Port Switching Module Front View of 18-Port Active Per-Port Switching Module 18-Port Active Per-Port Switching Module Side View . . . . . . . .
161. 162. 163. 164. 165. 166. 167. 168. 169. 170. 171. 172. 173. 174. 175. 176. 177. 178. 179. 180. 181. 182. 183. 184. 185. 186. 187. xii LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS LMS IP Panel . . . . . . . . . . . . . . . . . . . IP Port Address Table Panel . . . . . . . IP System Parameters Panel . . . . . . . . . . . . . . . . IP Port Parameter Panel . . . . . . . . IP Forwarding Table Panel IP Net To Media Table . . . . . . . . . . . . .
Tables 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. Copyright IBM Corp. 1995 Components of the 8250 Adapter Kit for 8260 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ethernet Pins on the 8260 Backplane 8260 controller Module LED Meaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D M M Status LED . .
xiv 8260 Multiprotocol Intelligent Switching Hub
Special Notices This publication is intended to help both IBM Customers and IBM System Engineers to install and configure the IBM 8260 Multiprotocol Intelligent Switching Hub. It contains description of the 8260 architecture as well as information about how to install, configure and manage the the 8260 Ethernet and token-ring modules. The information in this publication is not intended as the specification of any programming interfaces that are provided by IBM 8260 Multiprotocol Intelligent Switching Hub.
AIX IBM RS/6000 AIX/6000 NetView The following terms in this publication, are trademarks of other companies: Windows is a trademark of Microsoft Corporation. PC Direct is a trademark of Ziff Communications Company and is used by IBM Corporation under license. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.
Preface This document is intended to assist customers and IBM system engineers to implement local area networks based on the IBM 8260 Multiprotocol Intelligent Switching Hub. It contains description of the 8260 architecture as well as information about how to install, configure and manage the the 8260 Ethernet and token-ring modules.
This appendix provides information about the power requirements of the 8250 modules. Related Publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this document.
Acknowledgments The advisor for this project was: Mohammad Shabani International Technical Support Organization, Raleigh Center The authors of this document are: Mohammad Shabani International Technical Support Organization, Raleigh Center Nongyao Buranarachada IBM Thailand Mike Welsh IBM Australia This publication is the result of a residency conducted at the International Technical Support Organization, Raleigh Center.
xx 8260 Multiprotocol Intelligent Switching Hub
Chapter 1. An Overview of the IBM 8260 Hub This chapter is an introduction to the IBM 8260 Multiprotocol Intelligent Switching Hub. It is intended to provide the reader with an overview of the following: • Hardware description • Backplane architecture • Fault-tolerant power subsystem • Intelligent cooling subsystem • Distributed management architecture • Hot pluggability • Fault-tolerant controller module • Compatibility with the 8250 family 1.
• One power supply • One power supply bay cover • One AC power cord • Three fan units • One cable tray • One rack mount kit • One rubber feet kit • Six blank dual-slot filler plates • Three blank single-slot filler plates Additionally, you can order the following features to be included in your 8260: • Up to three additional power supplies for 8260 Model 017 and Model 17 A or up to two additional power supplies for the 8260 Model 010.
1.2 8260 Hardware Description There are three models of the 8260: • 8260-017 • 8260-010 • 8260-17A 1.2.1 IBM 8260 Model 017 The 8260 Model 017 is a 17-slot module which allows you to install any combination of 8260 and 8250 modules (except the 8250 Controller module) to set up token-ring, Ethernet and/or FDDI networks. Additionally, it can be upgraded with the ATM backplane to allow you to set up an ATM network.
Figure 1. IBM 8260 Model 017 1.2.1.2 Payload Area The payload area provides the housing for 17 media and management modules. In addition to the 8260 module, you may install all the 8250 modules (except the Controller module) in an 8260. Once these modules are installed on the 8260, they will be connected to the backplane. Certain modules provide you with per-port switching capability, which allows you to connect different ports on the same module to different backplane segments.
• Right Boundary Adapter: This adapter is a full length adapter and occupies one slot. Installation of this adapter results in 16 slots remaining available in the 8260 for the installation of media and management modules. It is recommended that you install this adapter in slot 17. The reason for this is that if an 8250 management module becomes the master management module, it will always see the Controller module installed in slot 17.
Table 1. Components of the 8250 Adapter Kit for 8260 Adapter kit Component 4-slot Feature 9-slot Feature 16-slot Feature Left Boundary Adapter 1 1 1 Right Boundary Adapter 1 1 1 Dual-Slot Top Filler 1 3 7 Single-Slot Top Filler 1 2 1 Dual-Slot Module Ejector Blocks 4 9 16 8250 Module Blank Faceplate 3 8 15 1.2.1.3 Fault-Tolerant Controller Module Slots The Controller module provides all the clocking signals for the 8260.
1.2.2 The Intelligent Cooling Subsystem The cooling subsystem consists of 3 fans, each of which cools a specific area of the hub. Each of the fans has a sensor to detect a slow or stopped condition and a temperature sensor to detect an over temperature condition. In conjunction with the Controller module and the DMM the hub environment can be monitored and controlled for over temperature conditions. Fan and Temp LEDs on the Controller module can also alert the user to potential problems.
• Model 010 is shorter than the Model 017 (498 mm versus 673 mm), but has the same depth and width. • Power supplies in the Model 010 are housed on the left side of the chassis whereas in the Model 017 they are housed in the bottom section. The 8260 Model 010 shares with the Model 017 all of the following benefits: • Supports three fan units. • Supports two Controller module slots for redundancy.
1.3.1.2 8260 Ethernet 20-Port 10Base-T Module The 8260 Ethernet 20-port 10Base-T module is single-slot module which provides 20 RJ-45 connectors for supporting 20 Ethernet ports. This module provides per-port switching capability. 1.3.1.3 8260 Ethernet 40-Port 10Base-T Module The 8260 Ethernet 40-port 10Base-T module is two-slot module which provides 40 RJ-45 connectors for supporting 40 Ethernet ports. This module provides per-port switching capability. 1.3.1.
1.3.2.2 8260 TR 18 Port Active Module Switching Module The 8260 TR 18 Port Active Module Switching module is a single-slot module which provides attachment of up to 18 workstations to one of the 10 token-ring segments on the ShuntBus using both STP and UTP cables. This module provides active re-timing and regeneration of the signal on every port. Ports 17 and 18 on this module can optionally be configured to act as fully repeated RI/RO trunk ports. 1.3.2.
1.3.3.2 8260 Fault-Tolerant Controller module The 8260 Fault-Tolerant Controller Module synchronizes the operations of all installed media and management modules by providing clocking and timing to the 8260 Multiprotocol Intelligent Hub Backplane. The Controller module is also responsible for managing the power and cooling subsystems. 1.3.3.3 Ethernet Media Access Daughter Card (E-MAC) The E-MAC daughter card allows you to gather statistics for the network to which it is attached.
12 8260 Multiprotocol Intelligent Switching Hub
Chapter 2. Backplane Architecture The 8260 backplane consists of the following two buses: • Enhanced TriChannel • ShuntBus These two buses are standard features of all the 8260 models and are installed on every 8260 shipped to the customers. The following sections provide detailed information about the 8260 backplane and how the backplane buses operate. 2.
Figure 3. Enhanced TriChannel Bus The number of pins available for user traffic on the ShuntBus is 72 pins. These pins are used to set up 2 dedicated Ethernet segments as well as 10 token-ring (or 4 FDDI) segments as shown in Figure 4 on page 15. On the ShuntBus, 8 pins out of the 72 network traffic pins are dedicated to be used by two Ethernet segments. These dedicated pins are not available to be used by other segment types.
Figure 4. 8260 ShuntBus 2.2 Ethernet Segments on the Backplane The 8260 allows you to set up a maximum of 6 Ethernet (ethernet_1 thru 6) segments on the Enhanced TriChannel and two Ethernet segments (ethernet_7 and 8) on the ShuntBus. ethernet_1 thru 3 can consist of 8250 and/or 8260 Ethernet modules, whereas ethernet_4 thru 8 can consist of 8260 Ethernet modules only. Each Ethernet segment on the backplane uses a number of pins on the backplane which is referred to as an Ethernet Path in this document.
SET MODULE {slot.sublsot} NETWORK {ethernet_n} or SET PORT {slot.port} NETWORK {ethernet_n} Before assigning the port or module to a network you may use the following management command to display the availability of the Ethernet segments on the Enhanced TriChannel and the ShuntBus: SHOW BACKPLANE_PATHS ETHERNET An example of the output from this command is shown in Figure 5.
segments ethernet_4, ethernet_5 and ethernet_6 on the Enhanced TriChannel and ethernet_7 and ethernet_8 on the ShuntBus. • Method 2: This method also uses 14 pins on the backplane to set up an Ethernet segment. In this method, each module attached to that Ethernet segment will use digital collision detection identical to that used in method 1. This means that the modules will send their slot-id in parallel over the backplane.
Table 2 (Page 2 of 2). Ethernet Pins on the 8260 Backplane Description Method 1 Method 2 Method 3 Slot ID bit 3 Y Y N/A Slot ID bit 4 (msb) Y Y N/A Serial ID N Y Y The following is a brief description of the use of each of the pins in an Ethernet segment on the 8260 backplanes: • Data enable signal : When this signal is active, data on the backplane is valid and the modules should receive and process the data on the ′Data in NRZ Format′ pin.
This pin is used to provide a means of detecting collisions of the segments using method 3. Analog collision detection is described in 2.2.2, “Analog Collision Detection” on page 19. 2.2.1 Digital Collision Detection Collision detection on the backplane (for methods 1 and 2) is done by using slot-id information transmitted on the backplane. Each module asserts its own slot-id one bit time before transmitting user data on the data pin.
• Data-in • Clock-in • Data-out • Clock-out When you assign an 8250 token-ring module to one of the token-ring networks on the Enhanced TriChannel (tr_8250_1 through tr_8250_7) using the following command: SET MODULE {slot.sublsot} NETWORK {token_ring_n} The 8260 will automatically allocate one of the available token-ring paths to this module. Note that you can neither choose the path used by the module, nor determine which path is used by a specific module.
the token-ring paths marked as ″available″ are the parts of the Enhanced TriChannel that are not currently used by any type of network. On the ShuntBus, in addition to the two dedicated Ethernet segments, there are 10 token-ring segments. Unlike, the Enhanced TriChannel, there is no concept of token-ring paths on the ShuntBus. Instead, there are 10 physical rings on the backplane.
• Data B transmit • Clock receive • Data A receive • Data B receive The reasons for two signals for each of the transmit and receive signals is given in 8.2, “8260 Backplane Signalling for TR Segments” on page 134. Note that regardless of the number of token-ring modules used in a segment, you always have the ability to set up 10 separate token-ring segments on the ShuntBus. The same pins that are used for token-ring segments on the ShuntBus are designed to be used for FDDI segments as well.
An example of the output from this command is shown in Figure 8 on page 23. 8260> Physical Path --------------FDDI_PATH_8250_1 FDDI_PATH_8250_2 FDDI_PATH_8250_3 FDDI_PATH_8250_4 FDDI_PATH_8250_5 FDDI_PATH_8250_6 FDDI_PATH_8250_7 FDDI_PATH_8250_8 show backplane_paths fddi Logical Network --------------in use in use in use in use in use in use in use available 8260> Figure 8.
• Any module can plug into any slot and all allocation of modules to networks or channels, regardless of whether they are TriChannel or Shunt Bus, is done by electronic switching (via DIP switches on the modules or management module commands). Figure 9 shows the Enhanced TriChannel network allocation and how the mixing of various network types affect the availability of the others. Figure 9.
Using Figure 10 on page 25 you can see that if, for example, fddi_1 network on the ShuntBus is used, it eliminates token_ring_1, token_ring_2 and token_ring_3. Also, you can see that the use of Ethernet segments ethernet_7 and ethernet_8 have no affect on the availability of token-ring and FDDI segments. Figure 10. ShuntBus Backplane Network Allocation Figure 11 on page 26 is a summary of how the Enhanced TriChannel and the ShuntBus are used to accommodate the various types of networks.
Figure 11. The Backplane Relationship between TriChannel and ShuntBus 2.5.1 Management Buses It was mentioned earlier that 42 of the 96 pins on the TriChannel Backplane are reserved for non-data traffic. Included in these pins are the Management LAN (MLAN) and the Serial Control Interface (SCI). 2.5.1.1 The Management LAN (MLAN) The MLAN is a dedicated 10 Mbps Ethernet bus which connects the DMM (Distributed Management Module) and all the Media Access Control daughter cards (E-MAC or T-MAC).
the MAC daughter card is accessed by the upper layer protocol stacks within the DMM (SNMP, Telnet) through the MLAN. The E-MAC can be installed on either the EC-DMM or the 8260 media modules. When installed on the 8260 media modules, E-MAC can collect statistics about all the Ethernet segments on the backplane, but will not be able to collect per-port or per-module statistics for the 8250 modules which are on Ethernet_1, 2 and 3.
28 8260 Multiprotocol Intelligent Switching Hub
Chapter 3. 8260 Fault Tolerant Controller Module The 8260 Fault Tolerant controller module is a critical component of the 8260. One active controller module is always required in order to keep the 8260 hub operational and running. Unlike the 8250 controller module, the 8260 Fault Tolerant Controller module does not occupy any of the payload slots because it resides on either slot 18 and/or 19 in the hub which are reserved for the controller modules.
3.1.1 The Controller Module Front Panel Figure 13. Front View of the Controller Module Figure 13 shows the front view of the controller module. Besides the hub reset and the LED test buttons, the controller module has 10 LEDs covering the 4 power supplies, 3 fans, active or standby mode and temperature on the front panel which indicate the state of the system environment. The names and locations of the buttons and LEDs are shown in Figure 13.
Table 3.
3.1.2 Controller Module Fault Tolerance There are two dedicated slots, 18 and 19, provided for installing the controller module. Once installed, the controller does not need to be configured. Since the controller module is a critical component, it is recommended to have a second controller module installed in the hub for backup purposes. When two controller modules are installed in the hub, one is active and the other will be a standby.
3.1.4 8260 Fault Tolerant Controller Module Considerations • Up to two controller modules can be installed in the 8260 hub. • Neither controller module occupies a payload slot. • When 2 modules are installed, one is active and the other is standby. • The hub reset button is only active on the active controller module. • The LED test button is active on both active and standby controller modules.
34 8260 Multiprotocol Intelligent Switching Hub
Chapter 4. 8260 Distributed Management Architecture This chapter will provide an in-depth look at the distributed management architecture of the 8260.
These daughter cards provide the following two functions: • Interface to the backplane segments To be able to communicate with devices attached to any of the backplane segments, DMM requires an interface to that segment. The interface to the Ethernet segments on the backplane is provided to DMM via E-MAC, whereas T-MAC allows DMM to interface with the token-ring segments on the ShuntBus.
Figure 14. Management Schematic The DMM (and daughter cards) provide management and control facilities in the following areas: − Configuration The DMM, networks, modules, and port settings can be configured through the DMM using DMM commands. The DMM can be used to configure 8250 as well as 8260 modules. − Statistics and fault reporting E-MAC and T-MAC provide support for collecting an extensive range of statistics based on RMON.
In a Simple Network Management Protocol (SNMP) managed environment the DMM acts as the SNMP agent, responding to SNMP requests and generating SNMP traps. − Telnet support Using Telnet you can log in remotely to any DMM on the network and manage it from the remote station. You can also use Telnet from the terminal attached to the DMM to log in to any other device which supports Telnet.
4.2 The Distributed Management Module (DMM) The stand-alone DMM is a single-slot management module that has no facility for carrying daughter cards. The DMM has 1 module status LED, a 4-character display with a display control toggle button and 2 serial port connectors as shown in Figure 15. Figure 15. DMM Front Panel 4.2.1 Unpacking and Installing the DMM Chapter 4.
Caution As always, great care should be taken when handling logic cards. The level of static electricity that can build up in the human body can be thousands of times greater than the very small switching voltage used in logic cards. An analogy would be connecting your Hi-Fi or TV set to 10,000 volts. It wouldn′ t last long! Remove the card from its shipping container and check it for damage. There are 2 jumper blocks that may need to be changed. Namely, JP8 and JP9 as shown in Figure 16.
Table 4. DMM Status LED LED name Color State Indicates Status Green OFF Power off or module failure ON Power on and software functioning properly Blinking Power on but diagnostics have failed The LCD display and display control button are used to: • Display the current operating state of the module • Determine the network assignment of ports and 8260 modules in the hub • Display the version of the DMM microcode The LCD display normally shows the module operating state.
The lower port is the auxiliary port and can be jumpered for RS-232 or RS-423 operation. This port allows you to attach a terminal locally (or via modem) to DMM. Note: The default is RS-232. See Table 7 on page 42 for the pinout of the cables used for attaching terminals to the auxiliary port. Table 7.
proper modem operation. See 4.2.4.3, “Configuring Terminal Settings for DMM” on page 47 for description of Set Terminal Hangup command. 4.2.4 Configuring the DMM The following table is a quick reference to the tasks required to configure the DMM interface. Table 9.
Table 10 (Page 2 of 2). DMM Terminal Defaults and Options Parameter Factory Default Options Stop Bits 1 1 or 2 Once the terminal has been configured press the Enter key. If the terminal has been configured correctly the following message should be displayed: 8260A Distributed Management Module (v2.10-H) Login: Figure 17. DMM Login Message To log in as superuser at the Login prompt type in system and press the Enter key.
8260A> set login password Enter current session password for user ″system″ : Enter new password: Verify - re-enter password: User password changed. 8260A> Figure 18. Changing Superuser Password Note: DMM passwords are case sensitive. You may define new login names with user, administrator and superuser authority. Figure 19 shows an example of how to define a new superuser.
8260A> show login Login Table: Index ----1 2 3 4 5 6 7 8 9 10 Login Name --------------system shabani admin1 user1 “not used“ “not used“ “not used“ “not used“ “not used“ “not used“ Access -------------Super User Super User Administrator User Active Sessions --------------1 0 0 0 Active Login Sessions: Login Name ---------system Session Type -----------Remote Super User Session Time -----------0 days 00:15:27 8260A> Figure 20.
Login: Login: system Password: A user with Super User or Administrator Access is already logged in. You are being logged in with User Access ... Welcome to user service on 8260A. 8260A> set login access super_user Super_user access granted. 8260A> Figure 21. Forced Termination of Existing D M M Users In this example, we tried to log in as a superuser and since there was already an administrator logged in, we got a user access.
Note: The baud rate specified in this command must match the settings of your terminal; otherwise, after issuing this command, the communication between the terminal and DMM will be lost. In that case, you must change the setting of your terminal before you can reestablish the communication. − Data_bits This parameter allows you to set the number of data bits used by DMM for communication with your terminal. The following command allows you to change the number of data bits to 8.
In this example, 9.67.46.3 is the address of the TCP/IP station attached to the DMM port. To use SLIP, you must also perform the following tasks: 1. Assign an IP address to D M M for communication over the SLIP interface. The following example defines 9.67.46.1 as the address used by DMM over the SLIP interface: 8260> set ip ip_address 9.67.46.1 slip 2. Assign an IP subnet mask to be used by D M M for communication over the SLIP interface. The following example defines 255.255.255.
This option is very useful in identifying the DMM to which you are logged in. The default prompt is ″ 8 2 6 0 > ″ . It is recommended that you use the same ID for both the terminal prompt and the DMM device name. See 4.2.4.4, “ Configuring DMM Device” on page 50 for how to configure DMM device name. • Set Terminal Timeout This command is used to specify the amount of time the terminal will remain active during the absence of keyboard activity.
This command sets the clock to 3:45 p.m., Thursday, Jan 19th, 1995. The clock is driven by an internal battery which is designed to last for 10 years. • Set Device This command allows you to configure the following for DMM: − Device name This command allows you to configure a name for DMM. It is recommended that each DMM in the network be assigned a unique name. The name can be a maximum of 31 characters long.
The factory default is for the DMM to run through a full set of diagnostics each time it is rebooted. By using the following command you can make the DMM bypass the diagnostics and boot up faster: 8260A> set device diagnostics disable − MAC address order In general, Ethernet devices uses canonical address format, whereas token-ring devices use a non-canonical address format.
You can configure DMM to force a mastership election when it is inserted into a hub. This option may be used to ensure that the DMM gets the opportunity to obtain the appropriate authority after it is removed and inserted back into the hub. The command to enable the forcing of mastership is as follows: 8260A> set device reset_mastership enable − DIP configuration Each 8260 media module has a set of DIP switches which allow you to configure how the module should operate.
Note that for your DMM to receive traps from the other stations, your DMM must be defined as a trap receiver in the community table of the other stations. After setting all the parameters for DMM you must ensure that you save them using the following command: 8260A> save device You can display the current device settings for DMM using the following command: 8260A> show device An example of the output from this command is shown in Figure 28.
For example, to assign a default gateway of 9.67.46.238 to the token_ring_10 segment on the ShuntBus, you must use the following command: 8260A> set ip default_gateway 9.67.46.238 token_ring_10 Note that DMM will use the IP address assigned to a segment to communicate through that segment. Therefore, if you have assigned IP addresses to more than one backplane segment, your DMM, effectively, has multiple addresses (one in each segment).
3. After configuring the IP address(es) for DMM, you must assign an E-MAC or T-MAC to any backplane through which the DMM is going to communicate using IP. For information about how to assign E-MAC or T-MAC to a backplane segment, please refer to 4.4, “MAC Daughter Cards” on page 61. 4.2.4.6 Configuring DMM SNMP Parameters The DMM acts as an agent in an SNMP managed environment, enabling you to manage the 8260 using an SNMP manager.
8260A> show community Index ----1 2 3 4 5 6 7 8 9 10 Community Name -------------------public public public public [empty] [empty] [empty] [empty] [empty] [empty] IP Address --------------***.***.***.*** 9.24.104.23 9.24.104.70 9.67.46.45 Access -----Read-Only All All All 8260A> Figure 30. Output from Show Community Command You can clear entries from the community table using the following command: 8260A> clear community index Where index is the number of the entry as shown in Figure 30.
8260A> set alert port_up_down {enable|disable|filter} If you enable this option, all the port up and port down traps will be sent to the local console. “disable,” prevents the traps from being displayed on the local console. “filter” allows DMM to check the ALERT_FILTER setting for each port for displaying/suppressing the port up and port down alters. The ALERT_FILTER for each port can be set using the following example: 8260A> set port 2.1 alter_filter {enable|disable} 4.
Figure 31. EC-DMM Front Panel 4.3.1 Installing the EC-DMM Remove the card from its shipping container and check it for damage. There are 2 jumper blocks that may need to be changed, JP8 and JP9. These jumpers are shown in Figure 32 on page 60. These jumpers allow you to set the auxiliary DB-9 connector to RS-232 or RS-423. For the factory default, which is RS-232, the jumper will be between pins 2 and 3 (the bottom 2 pins) of JP8.
Figure 32. Jumpering for the EC-DMM DB-9 Ports Holding the DMM by the faceplate, slide it into the slot in the 8260. Like all 8260 modules it can be hot plugged. If the EC-DMM has been installed correctly and is functioning the status LED should come on. The LCD display should show diag then either rdy for the master module or stby for a backup module. 4.3.2 EC-DMM LED Description Table 11.
Ethernet media module in slot 2 will also turn on to indicate those ports have been assigned to Ethernet_1. If there were more media modules with ports assigned to Ethernet_1 their port LEDs would also turn on.
daughter card to an isolated segment on a media module, the MAC daughter card must be installed on that media module. Note E-MACs installed on EC-DMM can collect detailed statistical information about all the ShuntBus and Enhanced TriChannel Ethernet segments. This statistical information includes network as well as module and port level information. This information is collected for both 8260 and 8250 Ethernet modules (note that 8250 Ethernet modules may attach to Ethernet_1 thru Ethernet_3 segments only).
3. The stand-alone D M M is always considered to be on the first subslot of the slot in which the stand-alone DMM is installed. Note that a stand-alone DMM does not have the housing for a MAC daughter card. 4. In the case of an EC-DMM which does have the housing for 6 E-MACs, the EC-DMM module is always considered to be in subslot 1 of the slot in which the EC-DMM is installed. Also, the DMM part of EC-DMM is always considered to be in subslot 8.
4.4.1 Ethernet MAC Daughter Card (E-MAC) E-MAC is a MAC daughter card which can be installed on an EC-DMM or Ethernet media modules. Figure 36 shows how you can install up to 6 E-MACs on a single EC-DMM. Figure 36. EC-DMM with Up to 6 EMACs In addition to the DMM with an interface to the network, E-MAC allows you to collect statistics about the Ethernet segment to which it is attached.
2. Use the following command to set an appropriate mode for the network interface on the E-MAC: 8260A> set module 2.2 interface {enable|disable|standby} The valid options for this command are: • Enable This option allows the network interface on the E-MAC to be activated automatically when attached to a backplane segments. An active E-MAC will be able to send and receive data and collect statistics about the segment to which it is attached.
In this example, the E-MAC is installed in the first subslot of the EC-DMM which is installed in slot 1 of the 8260. The output from this command is shown in Figure 38 on page 66. 8260A> show module 2.2 verbose Slot Module Version Network General Information ----- --------------- ------- ------------- ------------------02.02 E-MAC v2.
2. If you are planning to use LAAs within your network, use the following example to assign a locally administered address to T-MAC: 8260A> set module 6.2 locally_administered_address 40-00-00-82-60-a1 Note that assigning a locally administered address to T-MAC, does not result in the T-MAC using the assigned address automatically. You must use the following command to choose which type of MAC address (locally administered or universal) is to be used by the T-MAC: 8260A> set module 6.
T-MACs attached to the same segment and want one of them to act as a backup for the active T-MAC. 6. Assign the T-MAC to the desired segment using the following example: 8260A> set module 6.2 network token_ring_10 If you try to assign a T-MAC with enabled interface to a segment which already has an active T-MAC, your command will be rejected as shown in Figure 39. 8260A> set module 8.2 network token_ring_10 Interface module 6.
8260A> show module 6.2 verbose Slot Module Version Network General Information ----- --------------- ------- ------------- ------------------06.02 T-MAC v2.00 TOKEN_RING_10 T-MAC: Token Ring Network Monitor Card Boot Version: v2.00 IP Address: 9.67.46.235 Subnetwork Mask: ff.ff.ff.f0 Default Gateway: 9.67.46.
4.5.1 Managing 8260 with DMM The following is the summary of the capabilities of DMM when managing an 8260 which is populated with both 8260 and 8250 modules: 1. DMM can be used to fully configure the 8260 modules as well as the 8250. 2. DMM in conjunction with E-MAC can be used to monitor the network, module and port-level statistics for the Ethernet segments consisting of 8250 and 8260 modules.
segment. If multiple 8250 networks need to be monitored simultaneously then each network requires its own 8250 xMM. 8. The two previous points mean that the more monitoring required on 8250 networks the fewer payload slots are available for media modules. 9. ShuntBus based segments are not manageable by 8250 xMM. 4.6 Overview of Management and Control Commands Commands used in the 8260 hub can be organized into hierarchical or layer like structures.
72 8260 Multiprotocol Intelligent Switching Hub
Chapter 5. 8260 Intelligent Power Management Subsystem The 8260 provides extensive power management functions that allow you to take advantage of the modular load-sharing power supply system available on the 8260. This chapter provides detailed information about the power management subsystem of the 8260. 5.1 Intelligent Power Management Subsystem The 8260 comes standard with one load-sharing power supply but it allows you to have up to a maximum of four power supplies installed in a single 8260.
Figure 42. 8260 with 4 Power Supplies 5.2 Power Class Power class can be considered as a power priority which ranges from 1 to 10. 10 is the highest priority and 1 is the lowest priority.
with slot 1 to 17. The Controller module will repeat this process for all other power classes in descending order of their priority until either all the modules are powered up or the available power supply is exhausted. Note: You cannot assign a power class to the 8250 modules and they do not take part in the power management. This means that the Controller module cannot exert any control over the 8250 modules as far as the power management is concerned.
8260> show power slot all Power Management Information ---------------------------- Slot Power Information: Slot ---1 2 3 5 6 7 8 9 10 11 12 13 14 15 16 Class ----10 3 3 3 9 3 N/A N/A N/A N/A N/A N/A N/A N/A N/A Admin Status -----------ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE ENABLE Operating Status ---------------ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED ENABLED 8260>
Hub Information: Hub Type: 58G5801 Backplane Information: Backplane Type -------------Load-Sharing Power Distribution Board Enhanced TriChannel Backplane Ring Backplane Revision -------0 0 0 Power Supply Information: Power Supply -----------1 2 3 4 Status -----OKAY OKAY OKAY REMOVED Model Number -----------6000PS 6000PS 6000PS Temperature Information: Probe ----1 2 3 Location -------FAN_1 FAN_2 FAN_3 Temperature ----------27 Degrees Celsius 29 Degrees Celsius 27 Degrees Celsius Fan Information:
8260> show power budget Power Management Information ---------------------------Hub Power Budget : Voltage Type -----------+5V Voltage Level ------------5.196 Watts Capacity -------------551.00 Watts Available --------------287.00 Watts Consumed -------264.00 -5V -5.056 38.25 34.00 4.25 +12V 12.122 122.50 77.00 45.50 -12V -12.150 46.00 42.75 3.25 +2V 2.140 21.40 17.30 4.10 8260> Figure 47.
Note: If a power supply fails and there is still enough power in the hub to operate all the installed modules, the modules will continue their operation without any interruption. You can configure your 8260 to operate in non-fault-tolerant mode using the following DMM command: SET POWER MODE non_fault_tolerant The current power mode setting for your 8260 can be displayed using the following DMM command: SHOW POWER MODE An example of the output for this command is shown in Figure 48.
Table 14 (Page 2 of 2). Power Available to Modules in Fault Tolerant Mode Output Voltage One Power Supply Two Power Supplies Three Power Supplies Four Power Supplies -12.0 V N/A 18.00 W 30.50 W 46.00 W Totals N/A 293.40 W 520.30 W 779.15 W In fault-tolerant mode the 8260 does not reserve any specific power supply in reserve; instead, the reserved power is reserved across all the installed power supplies as shown in Figure 49.
5.4 Managing Power in the 8260 The 8260 fault-tolerant Controller module provides extensive power management functions for the 8260 and all its installed modules. However, the capabilities of the Controller module are enhanced via the power management facilities offered by DMM. The following sections examine the impact of DMM on managing the 8260. 5.4.
8260> 8260> show inventory HUB/ Slot Module ----- ---------------HUB 58G5801 Hardware Version Serial # Vendor Date -------- ---------------- ---------------- -----A H8048 ibm 940313 01.01 1 EC-DMM 1.0 B 1067067 IBM 940421 02.01 1 E24PS-6/8 02.02 E-MAC A D 1002683 1066450 ibm IBM 940302 940409 03.01 6706I-E XB2 XB26 Retix/Chip 042494 05.01 T20MS B 1291534 IBM 940805 06.01 T18PSA 06.02 T-MAC 06.03 T-JIT D A A 1292638 1293023 1070959 IBM IBM IBM 940811 940808 940810 07.
Figure 51. Installing 8260 Modules in an 8260 Managed by D M M 5.4.2 Installing 8260 Module in an 8260 Not Managed by DMM When a new 8260 module is inserted in the hub and there is no DMM installed in the 8260, the process of powering up the module is identical to what was described above. However, since there is no DMM, you will not be able to display the current power budget despite the fact that the Controller module has accurate information about the current power budget available in the hub.
2. The 8250 module sends module type information to the Controller module. The Controller module has no information about how much power is consumed by the module at this stage. 3. The Controller module forwards the module type of the newly inserted 8250 module to DMM. 4. DMM has a table which specifies the amount of power required by each 8250 module. This table contains an entry for each module Type . DMM retrieves the power requirements of the newly installed module from this table. 5.
5.4.4 Installing 8250 Module in a Hub Not Managed by DMM When a new 8250 module is inserted in a hub which is not managed by DMM, the process of applying power to the newly installed module is the same as what was described above. However, since there is no DMM, the Controller module is unable to acquire the power requirements of the 8250 module and to update its power budget table.
• When the hub is in the fault-tolerant mode, the reserved power is reserved across all installed power supplies. It is not an individual power supply out of all installed power supplies. • Although a power class does not apply to the 8250 module, the controller will see the 8250 module having the highest power class, 10.
8260> show hub Hub Information: Hub Type: 58G5801 Power Supply Information: Power Supply -----------1 2 3 4 Status -----NORMAL NORMAL FAULTY REMOVED Temperature Information: Probe ----1 2 3 Location -------FAN_1 FAN_2 FAN_3 Temperature ----------25 Degrees Celsius 25 Degrees Celsius 25 Degrees Celsius Fan Information: Fan --1 2 3 Status -----OKAY OKAY OKAY Figure 56. Using the SHOW HUB Command • Show Power Mode The show power mode command was used to show the current power mode.
system environment is changed and the power status has become non-fault tolerant due to a faulty power supply, as shown below. Message received from this device on 15:47 Mon 23 May 94: Enterprise Specific trap: Environment Change Message Information: Power Supply Status (3): FAULTY 8260> Message received from this device on 15:47 Mon 23 May 94: Enterprise Specific trap: Environment Change Message Information: Hub Power Fault-Tolerant Status : NON_FAULT_TOLERANT Figure 58.
DMM and a 24 PPS Ethernet module) and a number of 8250 modules. Both 8260 modules have a power class of 3 assigned to them. Upon taking one power supply down, we found that since the remaining power was not enough to power all the existing modules, the modules with the lowest power priority (the DMM and 24 PPS modules) were powered down by the Controller module. Note: There will be no message here since the DMM module has been powered-down. 5.
90 8260 Multiprotocol Intelligent Switching Hub
Chapter 6. 8260 Intelligent Cooling Subsystem This chapter provides you with information about the 8260 intelligent cooling subsystem. 6.1 Intelligent Cooling Subsystem The 8260 intelligent cooling subsystem is made up of a number of different components: • The fans and sensors • The DMM (Distributed Management Module) • The Controller module • The SCI (Serial Control Interface) All of these components work together to make up the intelligent cooling subsystem.
Each of the three fan units cools an overlapped area in the hub covering 8 slots. The slots covered by each fan unit are: • Fan 1 - slots 1-8 • Fan 2 - slots 6-13 • Fan 3 - slots 10-17 These 3 areas have their own temperature sensors. Also, integrated into each fan unit is a sensor that detects a stopped or slow fan condition. The Controller module continually monitors all the sensors via the SCI.
If a fan unit stops or the temperature in any of the three cooling zones rises above 60 C, the Controller module may, depending on a user configurable parameter (Overheat_Auto_Power_Down) use the SCI bus to power down some of the 8260 modules in the affected cooling zone in order to bring down the temperature to an acceptable level.
power class and slot position within the affected cooling zone as shown if Figure 63 on page 94. Figure 63. 8260 Cooling Zones and Power Classes • Modules are powered down until the 5 volt power supply consumption is reduced by 50 watts. • The temperature is allowed to stabilize for 15 minutes and if the temperature is still too high, all the 8260 modules in the affected zone are powered down. • When the overheat condition is resolved the modules are powered back up.
Figure 64. Flow Chart for an Overheat Condition Chapter 6.
96 8260 Multiprotocol Intelligent Switching Hub
Chapter 7. 8260 Ethernet Modules This chapter will describe the Ethernet modules for the 8260 multiprotocol intelligent switching hub. Each module will be described along with its features and the necessary steps required to configure these modules. Where necessary, examples will be given of where the module would be used.
to 16 times consecutively, after which the station reports a transmission error to the higher layer protocol. The probability of a collision occurring is directly proportional to the number of stations, frequency of transmissions, size of frames, and length of the LAN segment. Under the 802.3 specifications, no station can monopolize the network by sending more data than is allowed. Occasionally, a misbehaving application or a faulty adapter may transmit more data than is allowed.
7.2 8260 Ethernet 24-Port 10Base-T Module The 8260 Ethernet 24-Port 10Base-T Module is a 24-port IEEE 802.3 repeater module that complies with the 10Base-T standard and supports backbone and to-the-desk connectivity over Unshielded Twisted Pair (UTP) cabling. This module provides two 50-pin Telco-type connectors. Each Telco-connector can be connected to an external 12-port harmonica .
types of modules. For example, you can set a 10Base-T port on an 8260 Ethernet 24-Port 10Base-T Module to be a redundant port for 1 10Base-FB on the 8260 Ethernet 10-Port 10Base-FB Module. • Auto-polarity detection You can enable/disable auto-polarity detection for each port on the module. When enabled, this feature will automatically detect if you have erroneously reversed polarity of the cable during its assembly and will resolve the problem by reversing the polarity.
Figure 65. Front View of 24-Port 10Base-T Module Figure 65 shows the front view of the 8260 Ethernet 24-Port 10Base-T Module. As can be seen, the 8260 Ethernet 24-Port 10Base-T Module provides you with LED Indicators on the front panel that allow you to monitor the status of the module and the individual ports. Table 16 describes the meaning of these LEDs: Table 16 (Page 1 of 2).
Table 16 (Page 2 of 2). 24-Port 10Base-T Module LED Descriptions LED Name Color Activity Yellow Status Green State Description On Constant activity on the port Off No packets received on the port Blinking Normal activity on the port On Port enabled and link OK Off Port disabled. 1 Blink Link failure on the port 2 Blinks Port partitioned Figure 66 shows the side view of the 8260 Ethernet 24-Port 10Base-T Module.
Figure 67. 24-Port 10Base-T DIP Switches The DIP switches let you perform the following: • Use DIP switch positions 1 through 4 to assign all the ports on the module to one of the backplane segments or an isolated-1 segment. Note that when using DIP switches, all the ports will be assigned to the same segment, so you cannot do per-port switching when using DIP switches for configuring your the 8260 modules. Table 17 shows the meaning of settings for DIP switches 1 thru 4: Table 17.
4.2.4.4, “ Configuring DMM Device” on page 50. By default, DIP switch 5 is set to NVRAM. 7.3 10Base-T Module Usage Figure 68 provides an example of the usage of the 8260 Ethernet 24-Port 10Base-T Module. Figure 68. 24-Port 10Base-T Module Usage 7.
Each port on the 8260 Ethernet 24-Port 10Base-T Module can be enabled/disabled independently from the other ports. You can use the following management module command to enable/disable a port: SET PORT {slot.port} MODE {enable|disable} • Set port redundancy The port redundancy feature allows you set redundancy between two ports. The two ports can be on the same or different modules and can be of the same or different types.
7.5 8260 Ethernet 20/40-Port 10Base-T Module The 8260 Ethernet 20-Port 10Base-T Module, a single-slot 20-port, and the 8260 Ethernet 40-Port 10Base-T Module, a two-slot 40-port are IEEE 802.3 repeater modules that comply with the 10Base-T standard and support backbone and to-the-desk connectivity over Unshielded Twisted Pair (UTP) as well as Shielded Twisted Pair (STP) cabling.
• Support for port redundancy You can set up redundancy between two links on the same module or two different modules. Note that port redundancy is supported between different types of modules. For example, you can set a 10Base-T port on an 8260 Ethernet 20-Port 10Base-T Module to be a redundant port for a port on an 8260 Ethernet 10-Port 10Base-FB Module.
Figure 69. Front View of 20/40-Port 10Base-T Modules Table 19 describes the meaning of these LEDs: Table 19 (Page 1 of 2). 20/40-Port 10Base-T Module LED Descriptions LED Name Color Module Status Green Activity 108 8260 Multiprotocol Intelligent Switching Hub Yellow State Description On Module powered up OK Off No Power.
Table 19 (Page 2 of 2). 20/40-Port 10Base-T Module LED Descriptions LED Name Status Color Green State Description On Port enabled and link OK Off Port disabled. 1 Blink Link failure on the port 2 Blinks Port partitioned Figure 70 shows the side view of the 20/40-port 10Base-T modules. As can be seen, in addition to the 8 isolated segments and the mounting for two E-MACs, there is an 8-position DIP switch located on the module.
Figure 71. 20/40-Port 10Base-T DIP Switches The DIP switches let you perform the following: • Use DIP switch positions 1 through 4 to assign all the ports on the module to one of the backplane segments or an isolated-1 segment. Note that when using DIP switches, all the ports will be assigned to the same segment, so you cannot do per-port switching when using DIP switches for configuring the 8260 modules. Table 20 shows the meaning of the settings for DIP switches 1 thru 4: Table 20.
setting) will be sent to the management module. The actions taken by the management module, upon receipt of this information are described in 4.2.4.4, “ Configuring DMM Device” on page 50. By default, DIP switch 5 is set to NVRAM. 7.6 Configuring the 20/40-Port 10Base-T Modules To configure the 20/40-port 10Base-T modules you must do the following: • Select network for each port Each port can be assigned to one of the 8 Ethernet segments on the backplane or one of the 8 isolated segments on the module.
allows the port to receive signals compliant with 10Base-T standard. Low squelch level allows the port to receive weaker signals, enabling you to have longer distances, but increases the risk of losing packets due to the impulse noise. The maximum distances supported for UTP and STP cabling under different squelch settings are shown in Table 21. Table 21.
7.7 8260 Ethernet 10-Port 10Base-FB Module The 8260 Ethernet 10-Port 10Base-FB Module is a 10-port module that complies with the 10Base-FB standard and supports backbone and to-the-desk connectivity over fiber optic cabling.
information about the Ethernet security card, please refer to 7.11, “8260 Ethernet Security Daughter Card” on page 121. • Support for port redundancy You can set up redundancy between two links on the same module or two different modules. Note that port redundancy is supported between different types of modules. For example, you can set a 10Base-T port on an 8260 Ethernet 24-Port 10Base-T Module to be a redundant port for a 10Base-FB port on the 8260 Ethernet 10-Port 10Base-FB Module.
Figure 72. Front View of 10-Port 10Base-FB Module Figure 72 shows the front view of the 8260 Ethernet 10-Port 10Base-FB Module. As can be seen, the 8260 Ethernet 10-Port 10Base-FB Module provides you with LED indicators on the front panel that allow you to monitor the status of the module and the individual ports. Table 23 describes the meaning of these LEDs: Table 23 (Page 1 of 2).
Table 23 (Page 2 of 2). 10-Port 10Base-FB Module LED Descriptions LED Name Color Activity Yellow Status Green State Description On Constant activity on the port Off No packets received on the port Blinking Normal activity on the port On Port enabled and link OK Off Port disabled. 1 Blink Link failure on the port 2 Blinks Jabber 3 Blinks Port partitioned 4 Blinks Remote fault 5 Blinks Invalid data Figure 73 shows the side view of the 8260 Ethernet 10-Port 10Base-FB Module.
Figure 74. 10-Port 10Base-FB DIP Switches The DIP switches let you perform the following: • Use DIP switch positions 1 through 4 to assign all the ports on the module to one of the backplane segments or isolated-1 segment. Note that when using DIP switches, all the ports will be assigned to the same segment, so in effect, you cannot do per-port switching. Table 17 on page 103 shows the meaning of settings for DIP switches 1 thru 4: Table 24.
By default, the module is shipped from the factory with the DIP switches set for Ethernet_1. • Use DIP switch position 5 to choose if the module is going to use the Non-Volatile RAM (ON position) or DIP switch settings (OFF position) for its configuration. Note that if there is a management module installed in the 8260, this DIP switch determines which configuration (NVRAM or DIP switch setting) will be sent to the management module.
Note Using DIP switches on the 8260 Ethernet 10-Port 10Base-FB Module, it is only possible to assign all the ports to the same network. This network can be one of the 8 Ethernet segments on the backplane, or isolated-1. • Enable/disable ports Each port on the 8260 Ethernet 10-Port 10Base-FB Module can be enabled/disabled independently from the other ports. You can use the following management module command to enable/disable a port: SET PORT {slot.
This command may be used to allow you to monitor the status of the crucial ports on your network while the alerts from the other ports are disabled. • Set optical power Each port on this module can be set to operate at high or normal power. When operating at high power mode, the fiber distance between the two modules and the module or the transceiver can be as far as 4000 meters. Please note that you must enable high power mode at both ends to achieve the maximum possible distance.
7.11 8260 Ethernet Security Daughter Card The 8260 Ethernet Security Card (E-SEC) is a daughter card that allows you to provide security on any Ethernet network to which this card is attached. You can install this card on any Ethernet media module or the 8260 DMM with Ethernet Carrier (EC-DMM). Note Security features provided by this card are only applicable to the Ethernet ports on the 8260 modules.
ports may have one of these two features enabled and finally the last group of ports which may have no security at all. Details of configuring security features are described in 7.11.2, “Configuring the Security Module” on page 124. 7.11.1 Operation of Security Card When transmitting a packet, the 8260 Ethernet modules will use either method 2 or method 3 as described in 2.2, “Ethernet Segments on the Backplane” on page 15 for communication across the backplane. In both these methods: 1.
station attached to that port. The transmission of the jammed packet will last the same length of time as the original data packet. Stations that receive a jammed packet will discard it because the CRC (Cyclic Redundancy Check) field of the packet is incorrect. To perform intrusion control, the E-SEC card must perform the following: 1. Determine the source address of the station transmitting the data.
The entire process of eavesdropping protection takes 32 bit-times from the time the E-SEC card receives the destination address field in the packet. 7.11.2 Configuring the Security Module To be able to use the security module you must perform the following steps: 1. Assign the security module to the backplane segment on which you want to use the security feature.
• Enable auto-learning for your Ethernet segment using the following example: 8260A> set security network ethernet_3 auto-learning enable • Although the port and network auto-learning is enabled, the E-SEC module will not auto-learn MAC addresses attached to each port until you enable the security mode for the segment using the following example: 8260A> set security network ethernet_3 mode enable At this stage, the E-SEC module learns the addresses of all the stations attached to the ports for which you
wish the station shown in Figure 78 for this port to be able to access our network. The following command was used to delete this entry: 8260A> set security address_table address 10-00-5a-82-59-32 delete c. Once you are satisfied that the network address table contains all the desired entries, you can save this table on the non-volatile RAM of the E-SEC module using the following command: 8260A> save security address_table 4.
7. The following actions can be performed by the E-SEC card in case of intruder detection: a. Report intrusions by logging information about the intrusion in the intruder table. To enable intruder reporting, you must issue the following command: 8260A> set security network ethernet_3 intruder_reporting enable Note: When you enable intruder reporting only, the intruder will still be able to send data on the network, but an entry will be logged in the intruder table to report the intrusion.
and port jamming is enabled. You can use the following example to enable the failsafe feature for each port: 8260A> set security port 2.
Chapter 8. 8260 Token-Ring Support The 8260 token-ring support has been enhanced, compared to the 8250, to provide the following features: • Active re-timing per port • Speed detection by media modules • Beacon recovery by media modules • Address-per-port mapping This chapter will cover these features as well as some token-ring architecture background necessary to describe these features. It is beyond the scope of this book to provide detailed information about the token-ring architecture.
8.1.2 Ring Administration The token-passing ring protocol provides relatively greater control and management at the medium access control (MAC) level than that provided by the CSMA/CD protocol. All ring administration functions are implemented in the token-ring adapters and the functions are carried out at the MAC level. 8.1.2.1 Active Monitor In each operational ring, one station assumes the role of the active monitor . The process of active monitor selection is described in 8.1.2.
ring purge process may be triggered after detecting the loss of a token, frame, or errors caused by adapter-insertion or adapter-removal operations. To purge the ring, the active monitor initiates a Ring Purge MAC frame broadcast and starts the Ring-purge timer. If the Ring Purge MAC frame has not returned to the active monitor when the timer expires, the token-claiming process is initiated. 8.1.2.2 Token-Claiming Process This process is used to elect a new active monitor.
8.1.4 Differential Manchester Coding The 802.5 standard specifies that Differential Manchester coding is used for transmitting data on the ring. With this encoding technique, every bit is comprised of a half-bit time signal at a low or high polarity and other half-bit time signal at the opposite polarity. The mid-bit transition is for clocking only. The direction of the signal′s voltage transition will change whenever a ″0″ bit is transmitted and will stay the same for a ″1″ bit transmission.
The other important point about the Differential Manchester coding is that it uses a higher baud rate (the number of state changes on the transmission media) than the actual data transfer bit rate on the ring, to provide the benefit described above. In fact, the baud rate on the token-ring is twice the data transfer bit rate. On a 4 Mbps token-ring, the baud rate is 8 megahertz. A 16 Mbps token-ring runs at 32 megahertz. 8.1.
the signal passes from one station to another and ultimately can result in loss or corruption of data. This is a major reason for the limit on the maximum number of stations supported on a token-ring networks. Note that this limit varies depending on the speed of the ring and type of lobe cables used in attaching the workstations to the hub. Also, there is limitation on the type and the length of lobe cable.
Figure 81. Self-Shorting Relays on the ShuntBus Once a module is inserted into a slot in the 8260, the ShuntBus connector on the module breaks the shunt on the backplane. It is then the responsibility of the module to restore this connection by using a relay type function. When the module is not configured to connect to a backplane ring, the relay is set such that the backplane shunt is restored. At the same time, the signals transmitted by the module are looped back by the relay to the receive signals.
Mbps operation is different for the two bit-rates. For 4 Mbps operation, the encoding is straightforward. One of the data-signal shunt pairs (Data_A) carries the Differential Manchester encoded bit stream, whereas there is no signal on the other pair (Data_B). The clock shunt pair carries a synchronous clock which is used to sample the Data_A signal. Therefore, the maximum baud rate on the data pair for the 4 Mbps operation is 8 Mbaud and the clock frequency is 8 MHz.
Figure 83. 8260 Backplane Signalling for 16 Mbps Operation Note that the 8260 backplane interface is completely digital , whereas the signals sent on the transmission media (lobe cables and the cabling between two hubs) is said to be analog . In this context an analog signal is one where there is no separate clock signal. A digital signal is one where there are separate data and clock signals.
signal as the signal is clocked at 8 MHz on both the backplane and the transmission media (lobe cables and inter-wiring closet cables). 8.3 Dual Phase Lock Loop The intent of the dual PLL design of the 8260 is to isolate lobes from each other so the lobe length or type of cable will not affect what can be achieved on any other lobe of a ring segment. Below is a summary of the Dual PLL concept and its implementation in the 8260.
Figure 84. Components of Dual Phase Lock Loop The reduction in the jitter would allow you to have longer lobe distances and higher number of station per ring segment. More details about the number of supported stations and the lobe cable length are provided in 8.6, “Active Port Technology” on page 142. The DPLL is used in all the 8260 token-ring modules to ensure that the amount of jitter which enters the backplane has been minimized. This is the case with the passive modules as well as the active modules.
Figure 85. DPLL Implementation on Active Ports Note Since the jitter is removed from the signal before entering the backplane, the signal received from the backplane would only have a small amount of jitter accumulated on the backplane. The signal received from the backplane goes through the narrowband PLL before being transmitted out of the port. The passive module switching modules do not use DPLLs on each port.
8.4 Jitter Attenuator Daughter Card (JADC) The JADC can be mounted on any 8260 token-ring module and contains a DPLL function. It must be installed on a module under the following circumstances: 1. Your 18-port active module is configured with ports 17 and 18 acting as RI/RO ports and these ports are connected to a non-8260 hub. 2. The fiber ports on the dual-fiber repeater module are connected to a non-8260 hub.
wideband/wideband configuration when the port is in trunk mode. This is done to ensure that when the ring is reconfigured outside the module, a signal with a lot of accumulated jitter does not hit a wideband/narrowband configuration until it has gone through a JADC to remove the excessive jitter. So, the following is a summary of the differences between the active and passive modules. • A passive module has no active re-timing from port to port.
Note Please note that it is incorrect to say that we support 250 stations at 4 Mbps. That is not necessarily true since there are some adapters on the market that implement the minimum elastic buffer required for each workstation adapter card. These cards, while not affected by the rate of change of accumulated jitter (which has always been the limitation on station count) are not able to accommodate the worst case total absolute jitter that can accumulate.
backplane rings on the ShuntBus. This enables you to form multiple rings on a single module using this switch fabric. This is shown in Figure 87 on page 144. Figure 87. Token-Ring Per-Port Switching The rings to which the various ports on a per-port switching module can attach may be a mixture of 4 and/or 16 Mbps segments. Therefore, a single active module can be used to accommodate stations operating at different speeds.
Note With the 18-port active per-port switching module the lobe ports can be distributed concurrently across a total of 11 segments which can be a mixture of backplane token-ring segments and isolated segments on the module. However, on the same per-port switching module you cannot allocate an isolated segment number which matches the number of a backplane segment to which other ports on the module are attached.
5. Participation in neighbor notification By participating in the neighbor notification, the station learns the address of its Nearest Active Upstream Neighbor (NAUN). It also identifies itself to nearest active downstream neighbor. 6. Request initialization The station issues a Request Initialization MAC frame which will be sent to the Ring Parameter Server (RPS) functional address.
SET PORT {slot.port} STATIC_SWITCH {enable|disable} If you try to switch a port with enabled static switch from one segment to another, you will get the an error message. This is shown in Figure 89. 8260> set port 6.1 static_switch enable Port 06.01 static switch set to ENABLED. 8260> 8260> show port 6.1 verbose Port Display for Module T18PSA : Port Mode Status Network General Information ----- -------- ------------------- ---------------- -------------------06.
Figure 90. Port Switching with Source Routing Bridges 8.7 Signal Flow on the 8260 Token-Ring Modules On the module switching modules (active or passive), the signal flow is predefined on the module basis. That is, the signal which is received from the backplane is always passed to the first active port, then to the next active port, and finally from the last active port to the backplane.
8.8 Speed Detection Speed detection on the 8260 token-ring media modules is achieved in one of two ways depending on the module type. 8.8.1 Speed Detection on Active Modules For the active modules, speed detection is accomplished by counting the number of transitions in the incoming data over a set period of time. If the rate of transition is less than 4.5 MHz the station would only be allowed to enter 4 Mbps token-rings and if the rate of transition is more than 4.
• If the ″ A″ and ″C″ bits are not set to B′1′, the port which just inserted into the ring is assumed to be operating at the wrong speed. The Recovery ASIC will prevent that port from entering the ring and will also unwrap all the wrapped ports allowing the existing stations to resume their access to the ring. When an incorrect speed is detected on the inserting station, the port is wrapped and the status of the port is set to ″speed mismatch″.
8.9 Beacon Recovery 8.9.1 Introduction When a station detects a failure of token-claiming following a hard error, it transmits Beacon MAC frames with an all-station address to its ring, pacing them at a specified time interval known as ″T(transmit_pacing)″. This process will continue until the input signal is restored, or until this station removes itself from the ring for self-testing, as described below.
To ensure that TRMM has an accurate ring map, you must issue the following command for each port that has a MAC-less station (such as token-ring tracing tools) attached to it: SET PORT {slot.port} STATION_TYPE mac_not_present 8250 token-ring modules are shipped from the factory, with ″mac_present″ as default, which must be used for normal stations. You also need to issue the following command for each copper trunk port to ensure the correct port-to-address mapping: SET TRUNK {slot} RING_IN.
2. Isolate any new modules that have logical ports on the ring (logical is a port which cannot be disabled such as TRMM or bridge). 3. If the source or destination address in the packet is external to the hub, wait for up to 5 seconds to check if the beaconing can be disabled externally. 4. If the source or destination address in the packet is external to the hub, disable all external trunks. 5.
TRMM V3.0 allows you to enable/disable the beacon recovery function using the following command: SET DEVICE BEACON_RECOVERY {enable|disable} Note that this feature must be enabled during normal operation; however, you may disable this feature as a trouble shooting tool, to prevent the ring from recovering before the faulty device is isolated. TRMM V3.
8.9.3 Beacon Recovery in the 8260 Beacon recovery in the 8260 has been improved by distributing the beacon recovery process to each of the 8260 token-ring media modules (both active and passive). This allows you to manage an 8260 consisting of multiple token-ring segments using a single DMM and protect multiple rings from beacon problems without the need to have one DMM for each segment.
Figure 94. Recovery ASIC in Per-Port Switching Module You can find out the MAC address of the Recovery ASIC on each module by using the following DMM command: SH MODULE {slot.subslot} VERBOSE Figure 95 showsDisplay the output from this command for a 20-port passive token-ring module. 8260> show module 5.1 verbose Slot Module Version Network General Information ----- --------------- ------- ------------- ------------------05.01 T20MS v1.
8260> show module 6.1 verbose Slot Module Version Network General Information ----- --------------- ------- ------------- ------------------06.01 T18PSA v1.00 PER_PORT Trunk(s) are down T18PSA: Token Ring Active Port Switching Twisted Pair Module Boot Version: Ring Speed Dip Setting: Jitter Attenuator 1 Status: Non-Volatile DIP Setting: Recovery Asic Primary Address: Recovery Asic Secondary Address: Beacon Threshold: Switch ASIC type: v1.
Ring monitors are associated with each port and can be switched from upstream to downstream of that port. When the ring monitor detects a Beacon MAC frame on the ring, it calls in the Recovery ASIC to perform beacon recovery and isolate the faulty port (station). The following sections describe the beacon recovery procedures employed in the module switching modules and the per-port switching modules. 8.9.4 Beacon Recovery on the Module Switching Modules As described in 8.9.
detect this and will issue Beacon MAC frames. These Beacon MAC frames will be repeated by each station (station ″D″ in this case) until they arrive in the DRA in module 1. Upon seeing these Beacon MAC frames, the URA on module 1 will issue Beacon Type 1 MAC frames. The Beacon Type 1 MAC frames will be repeated by every station on module 2 (including the URA and DRA on module 2) until they arrive in the URA in module 1.
Monitor is attached. Once the Recovery ASIC is inserted into that ring, the DRA will be placed downstream of the last port of the module on the beaconing ring. Also, the URA will be inserted into the backup path if ports 17 and 18 are configured as trunk ports. Similar to the beacon recovery on the module switching module, the DRA will start transmitting Beacon type 1 MAC frames when it sees a Beacon MAC frame.
Now, DRA in ″TR Module 2″ starts tracking the stations that are involved in the neighbor notification process. The tracking will stop when the DRA in ″TR Module 2″ encounters an AMP/SMP MAC frame with the A/C bit set to B′0′, that is, AMP/SMP MAC frame issued by the NAUN to DRA. In this example, that would be the AMP/SMP MAC frame issued by station ″H″.
device on that port and therefore, the Recovery ASIC will be able to build the address-to-port map by listening to neighbor notification process as described above. Figure 99. Address-to-port Mapping on Module Switching Modules for Fan-Out Attached Devices Now, let′s assume that a second station (station ″C″) attaches to the fan-out device.
8260> show ring_map token_ring logical token_ring_1 Token Ring Logical Map for Network TOKEN_RING_1 MAC Address ----------------02-00-00-c0-cc-1c 02-00-00-c0-cc-0a 02-00-00-e0-9c-10 08-00-8f-40-01-a6 Slot ----05.01 05.01 05.01 05.01 Port ---1 2 2 3 8260> Figure 100. Address-to-Port Map Display for Fan-Out Attached Devices There could be situations, where the two MAC addresses between which the new station is inserted are on the same port.
8260> show ring_map token_ring logical token_ring_1 Token Ring Logical Map for Network TOKEN_RING_1 MAC Address ----------------02-00-00-c0-cc-1c 02-00-00-c0-cc-0a 02-00-00-e0-9c-10 08-00-8f-40-01-a6 00-00-00-00-00-00 Slot ----05.01 05.01 05.01 05.01 05.01 Port ---1 2 2 3 4 8260> Figure 101. Address-to-Port Map Display for MAC-less Stations 8.
2. An AMP/SMP MAC frame with the A/C bit set B′0′ is seen. This indicates that there is only one station attached to this port and the address of that station is one which is seen in the AMP/SMP MAC frame with the A/C bit set to B′0′. In this case, the AMP/SMP MAC frame sent by the upstream station is copied by the station attached to this port. Then the station attached to this port has issued its own AMP/SMP MAC frame which will pass this Ring Monitor with the A/C bit set to B′0′.
8260> show ring_map token_ring logical token_ring_2 Token Ring Logical Map for Network TOKEN_RING_2 MAC Address ----------------02-00-00-e0-9c-10 02-00-00-c0-cc-68 00-00-00-00-00-00 08-00-8f-d0-90-fa 02-00-00-66-88-8d Slot ----06.01 06.01 06.01 06.02 06.01 Port ---1 7 10 N/A 15 8260> Figure 103. Address-to-Port Map Display for a Per-Port Switching Module Note that in the above display, the module 6.01 is an active per-port switching module and the module 6.
As illustrated in Figure 104 on page 167, the dual-ring topology consists of two counter-rotating rings that provide interconnection for both dual-ring and single-ring stations. One of the rings is designated as the primary ring and the other ring is designated as the secondary ring . Figure 104. Dual-Ring Topology Normally, the primary ring is the operational ring and no data other than the MAC frames flow on the secondary ring.
Figure 105. Wrapback in Dual-Ring Topology 8.12.1 Trunk Wrapping on the Active Per-Port Switching Modules The 18-port active per-port switching module and the 10-port dual fiber repeater module conform to the 802.5C dual-ring reconfiguration practice. When, during the beacon recovery process, it is determined that the fault domain is between RI and RO, the following process takes place: 1. DRA is inserted on the primary path and URA is inserted on the backup path between RI and RO ports. 2.
Figure 106. Trunk Wrapping in Active Per-Port Switching Module 8.12.2 Trunk Wrapping on the Active Module-Switching Modules When, during the beacon recovery process, it is determined that the fault domain is between RI and RO, the following process takes place: 1. DRA and URA are inserted on the primary path. 2. RI/RO trunk is treated like a single lobe port. If wrapping the trunk pair fixes the fault, trunks are left wrapped. 3. URA and DRA are de-inserted. 4. D M M and Merge Manager (see 8.12.
Note On the 18-port active module switching module, the URA cannot be switched to the backup path. This means that the operation of this module is not IEEE 802.5C conformant. 8.12.3 Merge Manager The function of the Merge Manager is to periodically check RI and RO trunks to see if the cause of the beacon has been resolved and the trunks can be unwrapped.
Because these modules do not have switching capabilities, the URA cannot be switched onto the faulty segment. In order to execute the unwrapping tests, the module must wrap the backplane and wrap all the lobe ports. This allows the URA to be on a segment isolated with the trunk under the test. Obviously, this is disruptive to the stations on the module, so it is not desirable to try this every 5 minutes.
172 8260 Multiprotocol Intelligent Switching Hub
Chapter 9. 8260 Token-Ring Modules This chapter will describe the token-ring modules for the 8260 multiprotocol intelligent switching hub. Each module will be described along with its features and the necessary steps required to configure these modules. Currently, the available 8260 token-ring modules are: • 18-port Active Per Port Switching Module • 18-port Active Module Switching Module • Dual Fiber Repeater Module • 20-port Passive Module Switching Module • Jitter Attenuator Daughter Card 9.
Once the ring speed for the network is set, each port, trunk or module assigned to that network will assume the speed of the network.
• When ports 17 and 18 are configured as RI/RO ports, they are fully compliant with the IEEE 802.5C (dual-ring recovery) standard. • Support for installation of one T-MAC. • Support for installation of one Jitter Attenuator daughter card. Figure 108. Front View of 18-Port Active Per-Port Switching Module Figure 108 shows the front view of the 18-port active per-port switching module.
Table 28.
The DIP switches let you perform the following: • Use DIP switch positions 1 through 4 to assign all the ports on the module to one of the backplane segments or isolated-1 segment. Note that when using DIP switches, all the ports will be assigned to the same segment, so you cannot do per-port switching when using DIP switches for configuring your 8260 modules. Table 29 shows the meaning of settings for DIP switches 1 thru 4: Table 29.
Active Per-Port Switching Module Figure 110. Onboard Lobe/Trunk Jumpers on 18-Port Note that setting the jumpers to the left selects RI/RO and setting the jumpers to the right selects lobe ports. 2. Set beacon threshold for the module. When a beaconing condition is detected on a port, the port is wrapped by the recovery ASIC. The port is unwrapped when a transition of phantom is detected or when the port is disabled and then re-enabled by the administrator.
Use the following command to assign each port on the module to one of the backplane segments on the ShuntBus or isolated segments on the module: SET PORT {slot.port} NETWORK {network} 5. Assign RI/RO ports to network segments.
required. If a trunk fault appears which disrupts phantom drive, the trunk will wrap immediately. The module never goes to beacon recovery because the problem is corrected before that happens. If, for any reason, phantom is not disturbed by the fault, beacon recovery is initiated as in No. 1 above. To set the compatibility mode for a trunk, you can use the following command: SET TRUNK {slot} RING_IN COMPATIBILITY_MODE {mode} or SET TRUNK {slot} RING_OUT COMPATIBILITY_MODE {mode} 7.
passive module refer to 8.9.4, “Beacon Recovery on the Module Switching Modules” on page 158. • Support for address-to-port mapping using the Recovery ASIC. • Support for fan-out devices and splitters for attaching up to 8 stations to each port. Note that fan-out device or splitter is required to provide a phantom signal; therefore, an 8228 cannot be used as the fan-out device with this module. • Support for connection of MAC-less stations (such as token-ring tracing tools).
Figure 111. Front View of 20-Port Passive Module Figure 111 shows the front view of the 20-port passive module. As can be seen, this module provides LED indicators on the front panel that allow you to monitor the status of the module and the individual ports. Table 30 describes the meaning of these LEDs: Table 30 (Page 1 of 2).
Table 30 (Page 2 of 2). LED Name Port Status 20-Port Passive Module LED Descriptions Color Green State Description On Port enabled and operating normally on the ring Off Port disabled 1 blink Port enabled, no phantom Figure 112 shows the side view of the 20-port passive module. As can be seen, in addition to the 11 isolated segments and the mounting for one T-MAC, there is an 8-position DIP switch located on the module.
The number of times that a phantom transition is allowed to cause a port to unwrap is determined by the bcn_threshold parameter which can be set for each module using the following command: SET MODULE {slot.port} BCN_THRESHOLD {0-255} Once the threshold is exceeded, the port or trunk remains wrapped until the user disables and re-enables the port. While wrapped, the port status is BCN THRES EXCEEDED .
9.6 8260 Dual Fiber Repeater Module This is a single slot module that supports 10 active lobe ports and two sets of fully repeated fiber RI/RO trunk ports. This is a per-port switching module, which means that any of the lobe ports or and trunk port sets can be assigned to any of the backplane segments. The main features of this module are: • 10 lobe ports with shielded RJ-45 connectors. • Each lobe port has its own DPLL, which actively re-times and re-generates the signal on that port.
Figure 113. Front View of Dual Fiber Repeater Module Figure 113 shows the front view of the dual fiber repeater module. As can be seen, this module provides LED indicators on the front panel that allow you to monitor the status of the module and the individual ports. Table 28 on page 176 describes the meaning of these LEDs: Table 31 (Page 1 of 2).
Table 31 (Page 2 of 2). Dual Fiber Repeater Module LED Descriptions LED Name RI/RO JA1 and JA2 Port Status Color Green Green Green State Description On Trunk enabled and operating Off Trunk disabled.
9.6.1 Configuring the Dual Fiber Repeater Module To configure this module you must do the following: 1. Set beacon threshold for the module. When a beaconing condition is detected on a lobe port, the port is wrapped by the Recovery ASIC. The port is unwrapped when a transition of phantom is detected or when the port disabled and then re-enabled by the user.
Trunk ports can be enabled/disabled using the following command: SET TRUNK {slot} RING_IN.n MODE {enable|disable} or SET TRUNK {slot} RING_OUT.n MODE {enable|disable} 7. Enable/disable ports. Each port can be enabled/disabled using the following command: SET PORT {slot.port} mode {enable|disable} Chapter 9.
190 8260 Multiprotocol Intelligent Switching Hub
Chapter 10. 8260 RMON Support This chapter is intended to provide an understanding of the Remote Network Monitoring (RMON) concepts and to describe what facilities are provided by RMON to help you manage your Ethernet and token-ring LANs. These concepts are common to all RMON products though their implementation may differ. 10.1 RMON Overview The concept of remote network monitoring (RMON) was conceived to meet the requirements for truly distributed remote network management.
generation. Information provided by RMON can be used for identifying sources of network problems, for fine-tuning network performance, and planning for network expansion. RMON uses SNMP for communication between the network management station and RMON agents. Unlike SNMP devices, RMON keeps polling traffic overhead to a minimum as the RMON probes are not continuously polled. Note RMON provides a lot of statistical data detailing the network operations at the media level.
Figure 116. An Example of RMON Implementation 10.1.2 RMON Manager The network management station, also known as the RMON manager, works in conjunction with the RMON agents to provide a central point for managing and consolidating information gathered by the RMON agents. To minimize network overhead, the RMON manager does not continuously poll the agents although it has the ability to do so. The information collected by individual agents is transferred to the RMON manager at specified time intervals.
baseline network characteristics, quickly spotting potential trouble spots and resolving them before major crises occur. 10.2 RMON Goals To ensure that RMON can function effectively and efficiently in a distributed environment, its framework was designed with the following goals: • Offline operation • Preemptive monitoring • Problem detection and reporting • Value-added data • Multiple managers 10.2.
10.2.5 Multiple Managers The RMON framework permits the RMON agents to be managed by multiple network management stations concurrently. This is useful for implementing disaster recovery, and allowing different units or functions in the organization to access information provided by the RMON agents. For instance, the network planning group may want to continuously track the bandwidth utilization of each segment for capacity planning.
Table 32. MIB Structure for RFC 1271 - RMON M I B for Ethernet Group Statistics Description The Statistics group provides an overview of the current segment network activity at any given moment. It collects segment statistics like octets, packets, collisions, broadcast, various error counters and packet size. History The History group records periodic statistical samples from a segment and stores them for later retrieval.
memory and disk space to the RMON application. If you are running RMON subset on a bridge or router, you might want to consider offloading the task to an external monitoring device. Octets The number of octets of data (including those in bad packets) received on the network (including the FCS octets but excluding the framing bits). The term ″octet″ is used to refer to 8 bits. The term ″byte″ is not used because some devices have byte sizes greater than 8 bits.
Fragments Fragments are similar to CRC Align Error packets with the exception that each fragmented packet is less than 64 octets in length. This can indicate a high collision rate. Collisions The number of collisions detected on the network. Collisions are common phenomena on Ethernet segments. Excessive collisions are detrimental to network performance. It is an indication that you have too many stations trying to communicate simultaneously.
The History Control table stores configuration entries containing the interface information, polling period, number of buckets requested, and number of buckets granted. The number of buckets requested represents the number of times the operator wants to collect and store the samples. The probe will respond with the number of buckets granted based on the requests as well as available resources.
10.4.1.4 Host Group The Host group creates and maintains a host table for the segment monitored. The Host MIB is very useful as it contains information and cumulative statistics for every discovered host such as: • • • • • Host MAC address Good packets/octets received/transmitted Error packets transmitted Broadcast packets transmitted Multicast packets transmitted The information provided by the Host MIB is stored for each MAC host.
The Destination-Source table captures similar information but indexes it from a receiver-oriented perspective. 10.4.1.7 Filter Group The Filter group allows packets that are of particular interest to be captured using arbitrary filter expressions. These packets are then directed into channels that can be turned on or off to control the packet flow. The channels can also generate events when the packets are passing through them.
Table 33. MIB Structure for RFC 1513 - Token-Ring Extensions to the RMON M I B Group Token-ring Statistics History Description Token-ring MAC-layer Statistics This group collects ring error statistics and ring utilization from the MAC layer. It samples MAC data and provides information like MAC octets, MAC packets, beacon packets, line errors, burst errors, token errors, lost frame errors, congestion errors, etc.
Here is a list of MAC statistics available under this group and their respective descriptions: Drop Event The number of events in which MAC packets were dropped by the probe due to unavailability of resources on the probe itself. It doesn′t represent the number of packets dropped but the number of times this condition was detected. If the drop events counter constantly increments, it is an indication that there is more activity on the segment than can be captured by the network probe.
• • • Recovery mode set Streaming signal (not Claim Token MAC frame) Streaming signal, Claim Token MAC frame or intermediate detection of hard error Beacon Time Keeps track of the amount of time that the ring has been in the beaconing state. Beacon Packet Refers to the total number of Beacon MAC frames detected by the probe. Claim Token Event This counter keeps track of the total number of claim token events detected by the probe.
total number of burst errors reported in the Soft Error Report MAC frame. ACErrors This error is flagged when a frame is copied by an adapter to which it was not addressed. Address Copied Errors or ACErrors will increment the error counter only for the nearest upstream neighbor of the station reporting the error. This statistic is found in the total number of ACErrors reported in the Soft Error Report MAC frame.
Frequency Error Occurs when a ring station detects a frequency error. A new station inserting into the ring can cause downstream stations to be ″off frequency″. This condition seems to happen more on 16 Mbps than 4 Mbps rings. This statistic is found in the total number of Frequency errors reported in the Soft Error Report MAC frame. Token Error Token errors occur when a token is destroyed or corrupted. This usually occurs when devices insert or remove themselves from the ring.
or hub, you might want to consider offloading the task to an external monitoring device. Octets The total number of octets of data in good frames received on the network in non-MAC packets (including the FCS octets but excluding the framing bits). An octet represents an integral collection of eight bits of information. Packets The total number of non-MAC packets in good frames received on the network.
10.5.1.2 History Group The token-ring History groups capture historical information about network utilization and error statistics for the token-ring network. They provide a means of correlating the data collected by the Statistics group over time. They record statistical samples according to a user-specified frequency and duration and store them for later retrieval. The History MIB can be used to gather separate studies collected simultaneously from various probes and at different intervals.
• • • • • • • • • • • • • Line Errors Internal Errors Burst Errors Address Copied Errors Abort Errors Lost Frame Errors Congestion Errors Frame Copied Errors Frequency Errors Token Errors Soft Error Reports Ring Poll Events Active Stations All of the above statistics are also sampled by the token-ring MAC-layer Statistics group with the exception of the Active Stations statistic. For information about the individual statistics, please refer to 10.5.1.1, “Statistics Group” on page 202.
• • • • • • Number of active stations on the ring Current status of the ring with the following possible ring states: − Normal operation − Ring Purge state − Claim Token state − Beacon Frame Streaming state − Beacon Bit Streaming state − Beacon Ring Signal Loss state − Set Recovery Mode state Address of the last beacon sender Address of the last beacon sender′s NAUN Address of the Active Monitor on the segment List of all stations currently or previously detected to be physically present on this segment
10.5.1.5 Ring Station Configuration Group The token-ring Ring Station Config group provides the capability to actively manage and query the configuration of each token-ring node in the local ring. The RMON probe can initiate the removal of a station from the ring by sending a Remove Station MAC frame. It keeps the following configuration parameters of each station: • • • • MAC address Microcode EC level Group address Functional address 10.5.1.
source routing bridges. Transparent bridges do not use this field. One-Hop Frames Contains the total number of frames received whose route had one hop, were not all-routes broadcast frames, and whose source or destination address were on this ring. Two-Hop Frames Contains the total number of frames received whose route had two hops, were not all-routes broadcast frames, and whose source or destination address were on this ring.
following command to display the status of the DMM network interfaces via T-MACs and E-MACs installed in your hub: 8260A> show interface Figure 117 shows an example of the output from this command: 8260A> show interface Admin Oper MAC Idx Network Type Stat Stat Address Slot General Information --- ------------- ---- ----- ----- ----------------- ----- -------------------2 3 4 5 6 SLIP ETHERNET_1 ETHERNET_3 TOKEN_RING_10 TOKEN_RING_7 SLIP ETH ETH TR TR DOWN UP UP UP UP DOWN UP UP UP UP N/A 10-00-
• Host • History • Alarm • Event • Matrix • Statistics • TopN-hosts 10.6.2 Monitoring Functions Supported by T-MAC T-MAC V2.
Note The statistics that are collected using the DMM commands described in the next sections are NOT all RMON statistics. The non-RMON statistics are identified. 10.6.3 SHOW COUNTER Command for Ethernet Networks This DMM command allows you to display the following information for the segments to which the DMM has an interface via an E-MAC: 1.
8260A> 8260A> show counter interface ethernet_1 Interface Statistics for ETHERNET_1 ----------------------------------------------------------------------------Received Octets 939978 Received Unicast Packets 8488 Received Non-Unicast Packets 992 Received Discards 0 Received Errors 0 Received Unknown Protocols 0 Transmitted Octets 256 Transmitted Unicast Packets 0 Transmitted Non-Unicast Packets 4 Transmitted Discards 0 Transmitted Errors 0 8260A> Figure 119.
8260A> 8260A> show counter repeater ethernet_1 module 2 Repeater Statistics for Module 2 on ETHERNET_1 ----------------------------------------------------------------------------Readable Frames 0 Readable Octets 0 Runts 0 FCS Errors 0 Late Events 0 Short Events 0 Frame Too Longs 0 Very Long Events 0 Alignment Errors 0 Collisions 0 Data Rate Mismatches 0 Auto Partition Count 0 8260A> Figure 120.
8260A> 8260A> show counter rmon hosts ethernet_1 all RMON Hosts Table for Host Address 00-00-c9-01-01-0b on Port 2.4 ----------------------------------------------------------------------------Received Packets 136 Received Octets 8704 Transmitted Packets 190 Transmitted Octets 13132 Transmitted Errors 0 Transmitted Broadcast Packets 0 Transmitted Multicast Packets 54 RMON Hosts Table for Host Address 80-00-7a-00-00-a0 on Port 0.
• Statistics • TopN-hosts To be able to collect and view the above information, you must perform the following steps: 1. Use the ″SHOW INTERFACE″ command to determine the interface index for each E-MAC installed in your hub. 2. Enable the E-MAC interface if not enabled already. You can do this using the following command for the E-MAC: set module {slot.subslot} interface enable 3. Enable the RMON probe function of the E-MAC using the following command: set module {slot.
SET RMON ALARM ETHERNET {stat_type}.{interface} RISING {threshold} FALLING {threshold} {event} {time} {trigger} {alarm type} The following is a summary of the parameters that can be specified for the Stat_type: − BroadcastPackets − Collisions − CRCAlignErrors − Fragments − Jabbers − MulticastPackets − Octets − OversizePackets − Packets − UndersizePackets In the above command, event is the index number of the RMON event that occurs when the threshold is exceeded.
The format of the command to display the contents of the control table for the statistics group is slightly different. In this case, you must use the following command: SHOW RMON statistics ETHERNET CONTROL ALL The following example allows you to determine all the interfaces on which the RMON host group is enabled.
8260A> show rmon host data 1 all by_creation_order RMON Host display for Interface 3 : Creation Order Host Address Input Packets Output Packets Input Octets Output Octets Output Errors Output Packets (Broadcast) Output Packets (Multicast) : : : : : : : : : 1 10-00-5A-D4-B0-8C 2954 2954 301308 301308 0 0 0 Creation Order Host Address Input Packets Output Packets Input Octets Output Octets Output Errors Output Packets (Broadcast) Output Packets (Multicast) : : : : : : : : : 2 10-00-5A-82-5A-6A 2963
8260A> 8260A> show counter token_ring token_ring_7 Token Ring Statistics for TOKEN_RING_7 ----------------------------------------------------------------------------Ring Status: No Problems Detected Ring State: Opened Ring Open Status: Ring Open Ring Speed: 4 MBPS Upstream Station: 40-00-00-03-33-38 Functional Addr.
8260A> show counter interface token_ring_7 Interface Statistics for TOKEN_RING_7 ----------------------------------------------------------------------------Received Octets 6082132 Received Unicast Packets 19226 Received Non-Unicast Packets 93810 Received Discards 0 Received Errors 1 Received Unknown Protocols 0 Transmitted Octets 322275 Transmitted Unicast Packets 64 Transmitted Non-Unicast Packets 0 Transmitted Discards 0 Transmitted Errors 0 8260A> Figure 125.
8260A> show counter rmon hosts token_ring_7 all RMON Hosts Table for Host Address 40-00-00-03-33-38 on Port 6.
8260A> show counter rmon ring_station token_ring_7 ring RMON Token Ring Station Control Statistics for Network TOKEN_RING_7 ----------------------------------------------------------------------------Active Stations: 2 Table Size: 2 Ring State: Normal operation Last Beacon Sender: 00-00-00-00-00-00 Last Beacon NAUN: 00-00-00-00-00-00 Active Monitor: 40-00-00-03-33-38 Order Changes: 2 8260A> Figure 127.
8260A> 8260A> show counter rmon ring_station token_ring_7 all RMON Token Ring Station Statistics for Network TOKEN_RING_7 ----------------------------------------------------------------------------Station Mac Address: 40-00-00-03-33-38 Station Status: Active Last Enter Time: 1483081 Last Exit Time: 0 Last NAUN: 10-00-f1-0b-58-00 ----------------------------------------------------------------------------Duplicate Addresses: 0 In Line Errors: 0 Out Line Errors: 0 Internal Errors: 0 In Burst Errors: 0 O
SHOW COUNTER RMON TR_MAC_LAYER {network} An example of the output displayed for this command is shown in Figure 129.
8260A> 8260A> show counter rmon tr_promiscuous token_ring_7 RMON Token Ring Promiscuous Statistics for Network TOKEN_RING_7 ----------------------------------------------------------------------------Data Octets: 27092 Data Packets: 472 DATA PACKETS DATA PACKETSckets: 23 Broadcast Packets: 472 Multicast Packets: 02 18 to 63 Octets: 457 64 to 127 Octets: 15 128 to 255 Octets: 0 256 to 511 Octets: 0 512 to 1023 Octets: 0 1024 to 2047 Octets: 0 2048 to 4095 Octets: 0 4096 to 8191 Octets: 0 8192 to 18000 O
8260A> show counter rmon tr_source_routing token_ring_7 RMON Token Ring Source Routing Statistics for Network TOKEN_RING_7 ----------------------------------------------------------------------------In Frames: 0 Out Frames: 0 Through Frames: 1013 In Octets: 0 Out Octets: 0 Through Octets: 93748 All Rt Brcst Frms: 7477 Single Rt Brcst Frms: 18488 All Rt Brcst Octs: 553319 Single Rt Brcst Octs: 2624628 Local LLC Frames: 559 One Hop Frames: 0 Two Hops Frames: 0 Three Hops Frames: 0 Four Hops Frames: 0 Fiv
3. Enable the collection of RMON information by T-MAC, using the following command: SET MODULE {slot.subslot} RMON_GROUP enable This command enables the collection of RMON information by T-MAC. You must, also, enable the collection of individual RMON groups using the commands described in the next step. 4. Use the following commands to enable the collection of information for individual RMON groups by T-MAC: • Host group SET MODULE {slot.
8260A> 8260A> show module 8.2 verbose Slot Module Version Network General Information ----- --------------- ------- ------------- ------------------08.02 T-MAC v2.00 TOKEN_RING_7 T-MAC: Token Ring Network Monitor Card Boot Version: v2.00 IP Address: 9.67.46.195 Subnetwork Mask: ff.ff.ff.f0 Default Gateway: 0.0.0.
parameters, and remove stations on its ring. It also collects and forwards configuration reports generated by stations on its ring to the LAN manager. Traditionally, CRS and REM functions are implemented in the bridges.
8260A> show tr_surrogate 8.2 surr_status Surrogate Status Data for Network TOKEN_RING_7 -----------------------------------------------------------------------Surrogate Admin Status: ENABLED Port Mac Address: 10-00-f1-0b-58-00 Ring Segment: 0000 Ring Utilization: 0.0% REM Admin Status: ENABLED REM Oper Status: Active CRS Admin Status: ENABLED CRS Oper Status: Active 8260A> Figure 133. Displaying the Status of Surrogate Features 10.7.1.
8260A> show tr_surrogate 8.
An example of the output from this command is shown in Figure 136 on page 236. 8260A> show tr_surrogate 8.2 crs_station all Configuration Report Server Ring Station Data for MAC address 10-00-f1-0b-58-00 of Network TOKEN_RING_7 ----------------------------------------------------------------------------Station Status: Active Mfg.
SHOW TR_SURROGATE {slot.subslot} REM_SOFT_ERROR • Threshold exceeded conditions SHOW TR_SURROGATE {slot.subslot} REM_THRESHOLD_EXCD 10.8 DOT5_Group Support by T-MAC DOT5_Group support by T-MAC allows you to perform the statistics collection tasks defined in the IEEE 802.5 token-ring Management Information Base (MIB). These functions allow the T-MAC to perform the following: • Collect soft error statistics • Provide interface status information 10.8.
Table 35 (Page 2 of 2). Functions Performed by T-MAC V2.
Chapter 11. 8260 Multiprotocol Interconnect Module This chapter provides an overview of the routing and bridging functions provided by the Multiprotocol Interconnect module as well as discussing the steps required to configure the module to perform these functions. In this document, we have assumed that the reader is familiar with routing and bridging protocols. 11.
Note: DECnet Phase IV routing is not supported on token-ring ports. The Multiprotocol Interconnect module uses a 32-bit RISC processor (80960FA) for high performance, allowing you to forward up to 45,000 packets per second when bridging and up to 30,000 packets per second when routing IP. The performance of the module will vary depending on the number of routing protocols running in the module as well the size of the packets.
Figure 137 on page 241 shows the front view of the 1-slot and 2-slot Multiprotocol Interconnect modules. Figure 137. Front View of the Multiprotocol Interconnect Modules There are a number of activity and status LED displays on the front panel of the Multiprotocol Interconnect module which are used to show the information provided in Table 36 on page 242. Chapter 11.
Table 36.
Table 37 (Page 2 of 2). Power Requirements for Interconnect Module IP Cards Total Power Requirements (in Units) I/O Cards +2V +5V -5V +12V -12V 10Base-5 - 9 - 8 - 10Base-2 - 8 - 3 - 10Base-T - 7 - - - Token-Ring - 9 - - 1 It is expected that the customer will buy the Multiprotocol Interconnect module pre-configured with I/O cards, including proper programming for EEPROM, and will leave the I/O card configuration, as is, for extended periods of time.
Do you want to enter this into module x.y′ s EEPROM (Y/N): 8. Enter Y in response to the above prompt. 9. Remove the module from the 8260 and install the I/O card. 10. Return DMM to normal operation using the following command: BOOT 11. Install the module in the 8260. Now the module will report accurate power requirements of the entire module. 11.3 Bridging Functions This module can perform transparent bridging (TB) between Ethernet or 802.3 segments as well as between token-ring segments.
11.4 Routing Functions The Multiprotocol Interconnect module supports the following routing protocols: • IP • IPX • DECnet Phase IV 11.4.1 IP Routing Support When acting as an IP router, the Multiprotocol Interconnect module provides support for: • Directed broadcast • ICMP • Proxy ARP • Ethernet or 802.3 (not both) encapsulation on LAN interface • Datagram fragmentation/reassembly support • IP security • Boothelper • Static routes • Dynamic routes − RIP − OSPF 11.4.1.
• Supports authentication between routers. • Importation of RIP routes and static routes to an OSPF domain may be enabled or disabled. • Filters may be configured to import or discard specific RIP and static routes to OSPF. • Supports hop count to OSPF metric conversion when importing RIP and static routes. • Does not support non-broadcasting multi-access networks (such as X.25). 11.4.
command to assign ports 1 thru 6 to the desired Ethernet segments on the ShuntBus or Enhanced TriChannel. SET PORT {slot.port} NETWORK {ethernet_n|isolated} Note that ports 7 and 8 are not assigned to any segment on the backplane; therefore, the above command is not required for these ports. 11.6 Local Management System (LMS) When you connect to the Interconnect module via an ASCII terminal or Telnet session, you can have one of the following two types of sessions: 1.
• Configuration Menu This option allows you to alter configuration parameters and monitor statistics about the Multiprotocol Interconnect module. • Status Menu This option allows you to review the statistics and configuration information without changing any values. • Enable/Disable Write Access When you first access the LMS, you automatically have read-only access to monitor the Multiprotocol Interconnect module. Write permission is protected by a password.
* Help Screen Module: BladeRunner Time: 13:07 5 Jan 95 control-C: Cancel input, cancel a popup menu, or exit a screen control-J: Go to the screen jump table control-K: Go to this help screen control-L: Refresh the screen display control-P, control-T: Go to the top of the menu hierarchy control-W: Toggle write access for this session control-X: Jump to the equivalent screen in the other mode Exit Return to the previous screen Figure 139.
Config * Jump Table - Config screens System Phy. Port Protocol Bridging System Filtering Database Conversion System IP NetToMedia Table IP BootHelper DECnet Area Routing IPX System IPX Security List OSPF Area Def. Met. OSPF IF Metric OSPF RIP Convert OSPF St. Def. Conv. Download Phy. Port Interface Bridging Port Custom Filter Test IP System IP Forwarding IP Ping DECnet Routing IPX Port IPX Security Table OSPF Address Range OSPF Virtual IF OSPF RIP Def. Conv.
• Dot5 Group • Frame Relay Group • IP Forward Group • OSPF Group • PPPF Group • Retix Private MIB extensions The following SNMP traps will be sent by the SNMP agent to the SNMP managers which have been defined as a trap receiver . • coldStart • linkUp • Enterprise specific traps: • − frDCLiStatusChange − newRoot Retix Enterprise specific traps: − logicalPortUp − logicalPortDown − fpUp − fpDown − hardwareFail − temperatureOverheat − powerSupplyFail 11.
Config * Configuration Menu Module: BladeRunner Time: 14:24 5 Jan 95 System Menu Ports Menu Bridge Menu Protocols Menu Exit System parameters Menu Figure 141. LMS Configuration Panel The following sections will describe the required steps for configuring these features. 11.8.1 Configuring System Wide Parameters The system wide parameters allow you to configure the following: 1.
− Warmstart : All the configuration settings are read from the FLASH memory, resulting in the restoration of the last saved configuration information. Note that all the statistics tables will be cleared during to a Warmstart . The Menu Bar options of the Systems Parameters screen allow you to perform the following: • Reset Unit This enables you to initiate an immediate reset of the Interconnect module. When you choose this option, you will be prompted to enter Reset or Cancel to proceed.
To add an entry to this table, you must select Add Entry from the Menu Bar options of the panel shown in Figure 143 on page 254. You will then be prompted (via a pop-up menu) to enter the IP address and the community name of the SNMP manager. After entering this information you must select (on the pop-up menu) Set Entry to add this entry to the table or Cancel to abandon the operation. Config * Trap Destination Table System IP Address Module: BladeRunner Time: 15:21 5 Jan 95 Community Name 9.67.
Note If you select Start BOOTP Download and do not specify the TFTP server IP address and TFTP filename in the above panel, the Multiprotocol Interconnect module will use BOOTP to locate a BOOTP server in the network in order to get this information to perform the download operation. To perform download from a PC attached to the Multiprotocol Interconnect module′s serial port, select Start Serial Download . Config * Download Parameters System TFTP Server: 9.67.46.45 TFTP Filename: bld.
Config * Ports Menu Module: BladeRunner Time: 15:30 5 Jan Physical Port List Physical Port Protocol Parameters Physical Port Interface Parameters Logical Port Parameters Logical Port Multilink Parameters Exit Return to the previous screen Figure 145. LMS Port M e n u Panel The parameters shown in this panel are each applicable to certain environments as described below: • Physical Port List This option is applicable to all the WAN and LAN ports.
applicable to the LAN ports and will not be discussed any further in this book. 11.8.2.1 Configuring Physical Port Parameters The Physical Port List panel displays information about the physical ports currently installed on your module. An example of this panel is shown in Figure 146.
Config * Physical Port List Page 2 System Port ID Module: BladeRunner Time: 15:49 5 Jan 95 Name Connection Card Type Protocol 7 PHYSICAL PORT FRONT PANEL 1 tokenRing tokenRing 8 PHYSICAL PORT FRONT PANEL 2 tokenRing tokenRing Prev Page Next Page Exit Figure 147. LMS Physical Ports List for Token-Ring I/O Cards Using the Physical Port List panel, you may configure a name for each LAN port. To configure a particular entry, select the entry and press the Enter key.
Config * Phy. Port: 7 Physical Port Protocol Parameters PHYSICAL PORT Link Protocol: tokenRing Commands: noOp Ring Speed: fourMegabits Act Mon Part: false Funct MAC Addr Mask: C00000000000 Search Port Prev Port Module: BladeRunner Time: 15:56 5 Jan 95 Next Port Exit Return to the previous screen Figure 148.
11.8.2.3 Configuring Logical Port Parameters This panel allows you to configure parameters for Ethernet, token-ring and WAN logical ports. An example of this panel for an Ethernet port is shown in Figure 149. Config * Log.
• Encapsulation This is a read-only parameter and shows the type of encapsulation used on the physical port to which this logical port is attached. In the case of a token-ring port, this field will show tokenRing . • Attach Port and Detach Port These parameters are used to attach/detach logical ports to/from WAN physical ports. They are not applicable to LAN ports. 11.8.
The following sections describe the procedures used to configure the Multiprotocol Interconnect module to perform one of the following: • Transparent bridging for Ethernet and/or token-ring • Source-route transparent bridging for token-ring • Translational bridging between token-ring and Ethernet 11.8.4.1 Configuring for Transparent Bridging After configuring the system-wide and port parameters, you must do the following: 1. Select Bridging System Parameters from the Bridge Menu .
− Time-To-Delete (in seconds) For information on this parameter, refer to 11.8.5, “Filtering for Bridging Functions” on page 270. − Time-To-Forget (in seconds) For information on this parameter, refer to 11.8.5, “Filtering for Bridging Functions” on page 270. • You must ignore the following parameter as it does not apply to LAN only Multiprotocol Interconnect module: − Adaptive Routing Support 2. Select Transparent Bridging Port Parameters from the Bridge Menu .
If security mode is disabled , and the destination address is known, the packet is forwarded on the appropriate port. If the address is not known, the packet is sent (flooded) on all the other ports. For more information, refer to 11.8.5, “Filtering for Bridging Functions” on page 270. • Custom Filtering This option allows you to enable or disable custom filtering for the packets received on this port.
Config * STP System Parameters System STP Facility: Enabled STP Version: draft STP Domain Address: 0180C2000000 Reset Delay Time: 120 Bridge Priority: 8000 Bridge Hello Time: 400 Bridge Max Age Time: 1200 Module: BladeRunner Time: 17:06 5 Jan 95 Bridge Forward Delay Time: 800 Exit Version of the Spanning Tree Protocol Figure 153.
If two bridges have the same bridge priority, the one with the lowest MAC address has higher priority. • Bridge Max Age Time Specifies the max value for the age field (in hundredths of a second) in the Hello BPDU before it is discarded by the Multiprotocol Interconnect module. This value will only be used (by all the bridges in the spanning tree as well as the Multiprotocol Interconnect module) should this module become the root bridge.
• Path Cost Mode This parameter is used by the spanning tree protocol to determine how the value of the path cost is configured. The following values can be specified for this parameter: − Manual : In this case the path cost will be taken from the Manual Port Path Cost parameter. − High : The path cost will be determined by the 1000/LineSpeed formula. − Normal : The path cost will be determined by the 100/LineSpeed formula. − Low : The path cost will be determined by 10/LineSpeed formula.
Config * Log. Port: 8 Source Routing Port ParametersModule: BladeRunner LOGICAL PORT Time: 17:33 5 Jan 95 Security Mode: Disabled Source Address Filtering: Disabled Custom Filtering: Disabled Hop Count: Local Segment: Disabled Largest Frame: mtu4472Bytes Search Port * Port STE SpanMode: Prev Port Next Port autoSpanMode Exit Return to the previous screen Figure 155.
5. Configure the STP Port Parameters for each token-ring port performing source-route transparent bridging, as described in 11.8.4.1, “Configuring for Transparent Bridging” on page 262. 6. Optionally, you may configure the security and filtering parameters as described in 11.8.5, “Filtering for Bridging Functions” on page 270. 11.8.4.
This parameter allows you to enable/disable SNAP conversion between token-ring and Ethernet frames. When enabled, the Ethernet network is treated as an 802.3 network. When disabled, the Ethernet network is treated as an Ethernet V2 network. Note that the implication of this parameter is that the Ethernet ports can be either Ethernet V2 or 802.3 but not both. • IPX Conversion When enabled , IPX packets are recognized and processed by the module for bridging between token-ring and Ethernet.
Config * Filtering Database Page 1 System MAC Address Disposition #0000B528023E 1 %0180C2000000 #08005A1326EB 2 %08008F4001A0 %08008F4001A1 %08008F4001A2 %08008F4001A3 %08008F4001A4 %08008F4001A5 %08008F4001A6 %08008F4001A7 %090077000001 + Unlearned # Learned Add Entry Scope MAC Address all Module: BladeRunner Time: 14:27 6 Jan 95 Disposition Scope %090077000002 all * Static Freeze Database $ Permanent Search Addr % Management Prev Page Next Page Return to the previous screen
− Permanent($) These are manually entered addresses which are stored in the FLASH memory. − Static (*) These are entries that have been entered manually. They cannot be aged-out of the filtering database, but will be lost during a module Reset . Usually the manually entered addresses are permanent and are retained in the FLASH memory which results in them being retained during the module reset. But, if the FLASH is too full to store the address, that address becomes static.
To do this, each address in the database has an age assigned to it. When the address is learned, the age is set to zero. At subsequent time intervals this address is incremented.
11.8.6 Destination Address Filtering Destination address filtering allows you to use the contents of the filtering database to forward or discard frames. Destination address filtering is always performed by the Multiprotocol Interconnect module.
Filter Test Table . Note that there is only one of these tables in each Multiprotocol Interconnect module and it contains all the test that are to be performed by the Multiprotocol Interconnect module, regardless of the ports on which these tests are performed. To define the tests, select Custom Filter Test Table from the Bridge Menu . An example of the panel displayed is shown in Figure 158.
This field defines the bits in the received frame, starting at the specified offset , that should be tested against the contents of the value field. Only the bits which have a value of B′1′ in the mask will be tested. • Logical Operator The following operators can be used for testing: • − Equal − Not_equal − Less_than − Greater_than Value This field specifies the 32-bit unsigned value against which the contents of a frame starting at the specified offset should be compared.
Config * Log.
− Fwd Prio #: Forward the frame at the specified priority (#). # can be 0 to 7. Priority 0 is the highest priority. − Stmt #: Specifies another statement ID from the Custom Filter Statement Table, so that another test may be applied to the frame. # can be 1 to 16. An example of the use of priority is to check for the frame size and assign higher priority for shorter frames (typically interactive sessions) over the longer frames (typically batch/file transfer sessions).
The following sections describe the procedures used to configure the Multiprotocol Interconnect module to perform one of the following: • IP routing • IPX routing • DECnet Phase IV routing 11.8.8 Configuring for IP Routing The Multiprotocol Interconnect module allows you to use RIP, OSPF, and static routes when used as an IP router. To configure the Multiprotocol Interconnect module as an IP router you must do the following: 1.
Config * IP Port Address Table Page 1 System Port 1 1 2 IP Address 9.67.46.11 9.67.46.44 9.67.46.17 Add Entry Module: BladeRunner Time: 15:35 9 Jan 95 IP Subnet Mask 255.255.255.240 255.255.255.240 255.255.255.240 Prev Page Next Page Exit Return to the previous screen Figure 162. LMS IP Port Address Table Panel This table allows you to view and/or modify the IP addresses assigned to each port.
An example of the IP System Parameters panel is shown in Figure 163 on page 281. Config * IP System Parameters System IP Routing: Enabled RIP: Enabled Module: BladeRunner Time: 15:43 9 Jan 95 Router ID: 9.67.46.44 IP Security: Disabled ARP Timeout: 1500 Reassembly Timeout: 10 Proxy ARP: Disabled Source Quench: Disabled Redirect: Disabled ICMP tx rate: 1000 Hash Size: 512 Default TTL: 16 Exit Return to the previous screen Figure 163.
This parameter specifies the length of time that the module may wait for all the fragments of a fragmented IP message to be received for reassembly. If they are not received within the specified time, the datagram is discarded. Note that datagram reassembly takes place at the destination of a datagram only.
Config * Log. Port: 1 IP Port Parameters LOGICAL PORT IP Port Routing: Enabled RIP: Enabled Disposition: discard IP Mtu: 1492 RIP Path Cost: 1 LAN Encapsulation: ethernet Broadcast Form: ones Forward Broadcast: Enabled * Security Access List 1: 0 Search Port Module: BladeRunner Time: 15:55 9 Jan 95 Security Access List 2: 0 Prev Port Next Port Exit Return to the previous screen Figure 164.
that the Multiprotocol Interconnect module recognizes both types of broadcasts on the received frames regardless of the setting of this parameter. • Forward Broadcast This parameter specifies if this port will forward directed broadcast messages. Directed broadcasts have all 1′s in the hostid portion of their address. • Security Access List n This parameter specifies the security access list associated with this port. You may assign two security access lists with a single logical port.
• Next Hop This is the IP address of the node that is the next stop for a packet en route to its destination address. The next hop must be directly connected to the interface for which this route is defined. • Mask This is the subnet mask associated with the destination address entry. • Type This field indicates whether the destination address is directly connected to this interface.
Config * IP Net To Media Table Page 1 System Port 1 1 1 1 1 1 Module: BladeRunner Time: 10:50 11 Jan 95 Network Address Media Address Type 9.67.46.13 9.67.46.33 9.67.46.34 9.67.46.40 9.67.46.41 9.67.46.46 400000000001 10005A7903C7 10005A7903E1 0000B528023E 08008F3003EF 08005A13396F static dynamic dynamic dynamic dynamic dynamic Add Entry Search Addr Prev Page Next Page Exit Add a new entry to the IP Net To Media Table Figure 166.
Also a BOOTP client can request the code image file to be downloaded from the TFTP server. To configure the Multiprotocol Interconnect module as a Boothelper you must select Boothelper Parameter from the Protocols Menu . An example of the Boothelper Parameters panel is shown in Figure 167. Config * Boothelper Parameters System Module: BladeRunner Time: 10:51 11 Jan 95 Boothelper: Enabled Forward Address: 9.67.46.45 Hop Count: 3 Exit Return to the previous screen Figure 167.
11.8.8.1 Configuring for OSPF To configure the Multiprotocol Interconnect module to use OSPF, you must select OSPF from the Protocols Menu . The resulting panel is shown in Figure 168.
Config * OSPF System Parameters System Area Border Router: false Router ID: 9.67.46.44 TOS Support: true Admin Status: Enabled AS Boundary Router: true Import Rip Routes: Enabled Import Static Routes: Enabled Default Action on No Match for RIP Routes: Module: BladeRunner Time: 17:39 11 Jan 95 import Default Action on No Match for Static Routes: import Exit Return to the previous screen Figure 169.
This parameter determines if the RIP filter table will be used for importing routes found by RIP. RIP filter table is discussed later in this section. • Import Static Routes This parameter determines if the static route filter table will be used for importing static routes. Static route filter table is discussed later in this section. • Default Action on No Match for RIP Routes This parameter specifies the action to be taken when a RIP route does not match any entry in the RIP filter table.
can only be modified. There will be one entry in this table for each IP address assigned to the Multiprotocol Interconnect module′s ports. To modify the parameters on this panel, you must select the Modify Entry option. A pop-up menu will be displayed which allows you to change the following parameters for each IP interface: • IP Address This parameter specifies the IP address of the port. This parameter must be one of the IP addresses currently displayed on the panel.
This parameter specifies the number of seconds between the Hello Packets that the router sends on the interface. This interval must be the same for all the routers attached to the same network. • RtdDeadInt If a router′s neighbor does not see a Hello packet within this period, it will declare the router down. The Dead Interval should be some multiple of the Hello Interval. • AuthKey This is the character string that will be exchanged between the routers to perform partner authentication.
Config * OSPF Area Table Page 1 System Area ID AuthType 0.0.0.0 1 Import AS SPF Extern LSA Runs true 10 Add Entry Prev Page Module: BladeRunner Time: 17:41 11 Jan 95 Brdr AS Brdr Area Routers Routers LSAs 0 1 3 Next Page Chksum Sum 025393 Exit Return to the previous screen Figure 171. LMS OSPF Area Table Panel This table contains information regarding the various areas in the AS.
This parameter is read-only and contains 32-bit unsigned sum of the Link-state-advertisement′s link-state checksum contained in this area′ s link-state database. This sum can be used to determine if there has been a change in a router′s link-state database and to compare the link-state database of two routers. Note: Area 0.0.0.0, by definition, is the backbone area and is always present in the OSPF area table. 4.
from the OSPF Menu . The resulting panel is shown in Figure 173 on page 295. Config * OSPF Address Range Table Page 1 System Area ID Range Net Range Mask 0.0.0.0 9.67.46.0 255.255.255.000 Add Entry Prev Page Module: BladeRunner Time: 12:04 11 Jan 95 Next Page Exit Return to the previous screen Figure 173.
Config * OSPF Interface Metric Table Page 1 System Module: BladeRunner Time: 17:44 11 Jan 95 IP Address Port TOS Metric 9.67.46.17 9.67.46.44 9.67.46.94 0 0 0 0 0 0 10 10 10 Add Entry Prev Page Next Page Exit Return to the previous screen Figure 174. LMS OSPF Interface Metric Table This panel allows you to specify the following parameters for each entry: • IP Address This is the IP address of the interface advertising the metric.
Config * OSPF Virtual Interface Table Module: BladeRunner Page 1 Time: 17:44 11 Jan 95 System Area ID Neighbor Add Entry TransDelay RetransInt Prev Page HelloInt Next Page RtrDeadInt Exit Return to the previous screen Figure 175. LMS OSPF Virtual Interface Table Panel The following parameters can be specified for each entry: • Area ID This parameter specifies the 32-bit integer identifying the transit area that the virtual link traverses. By definition, this is not 0.0.0.
8. Define the other OSPF routers which are neighbors to the Multiprotocol Interconnect module. To so so, select OSPF Neighbors from the OSPF Menu panel. An example of the resulting panel is shown in Figure 176 on page 298. Config * OSPF Neighbor Table Page 1 System Module: BladeRunner Time: 17:45 11 Jan 95 IP Address Port Router ID Options Priority State 9.67.46.46 0 0 9.24.104.
This field is read-only and shows the current length of the retransmission queue. 9. You may define the filters for importing RIP discovered routes by selecting OSPF RIP Filter Table from the OSPF Menu . An example of the resulting panel is shown Figure 177. Config * OSPF Rip Filter Table Page 1 System IP Address IP Mask Action 9.67.46.0 255.255.255.240 import Add Entry Prev Page Module: BladeRunner Time: 17:45 11 Jan 95 Next Page Exit Return to the previous screen Figure 177.
Config * OSPF Rip Convert Table Page 1 System Module: BladeRunner Time: 17:46 11 Jan 95 IP Address IP Mask Hop Count Metric 9.67.46.0 9.67.46.0 9.67.46.0 9.67.46.0 9.67.46.0 9.67.46.0 9.67.46.0 9.67.46.0 9.67.46.0 9.67.46.0 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.240 255.255.255.
Config * OSPF Rip Default Convert TablModule: BladeRunner Page 1 Time: 17:47 11 Jan 95 System Hop Count Metric 1 2 3 4 5 6 7 8 9 10 10 20 30 40 50 60 70 80 90 100 Modify Entry Prev Page Next Page Exit Return to the previous screen Figure 179. LMS OSPF Default RIP Convert Table Panel The following parameters can be viewed/modified for each entry: • Hop Count This parameter specifies hop count measured in RIP. • Metric This parameter specifies the metric in OSPF converted from RIP.
Config * OSPF Static Filter Table Page 1 System IP Address IP Mask Add Entry Module: BladeRunner Time: 17:47 11 Jan 95 TOS Prev Page Next Page Action Exit Return to the previous screen Figure 180. LMS OSPF Static Filter Table Panel This panel allows you to define the following parameters for each filter entry: • IP Address This parameter specifies the destination IP address. • IP Mask This parameter specifies the mask associated with the IP address.
Config * OSPF Static Convert Table Page 1 System IP Address IP Mask Modify Entry Module: BladeRunner Time: 17:48 11 Jan 95 TOS Prev Page Hop Metric Next Page Exit Return to the previous screen Figure 181. LMS Configuration Panel This panel allows you to enter the following parameters for each entry: • IP Address This parameter specifies the destination IP address. • IP Mask This parameter specifies the destination IP address mask.
Config * OSPF Static Default Convert TablModule: BladeRunner Page 1 Time: 17:49 11 Jan 95 System TOS Hop Count Metric 0 0 0 0 0 0 0 0 0 0 1 2 3 4 5 6 7 8 9 10 10 20 30 40 50 60 70 80 90 100 Modify Entry Prev Page Next Page Exit Return to the previous screen Figure 182. LMS OSPF Default Static Convert Table Panel The following parameters can be viewed/modified for each entry: • Hop Count This parameter specifies hop count measured in RIP.
Config List: * 1 IP Security Table Page 1 ID Source Address Source Mask 1 9.67.46.41 255.255.255.240 9.67.46.46 Add Entry Search List Destination Address Prev List Next List Module: BladeRunner Time: 12:02 18 Jan 95 Destination Mask Action Prot 255.255.255.240 pass Prev Page Next Page ip Exit Return to the previous screen Figure 183.
• Source Address This is the source address of the IP datagram against which the source address of the IP datagram currently being processed is compared. A value of 0.0.0.0 serves as a wildcard, indicating all IP addresses. • Source Mask This is the address mask which is logically ANDed with the source address in the table and the source address in the IP datagram. The two results are then compared using the operator parameter.
Config List No.
• ICMP Generation This field specifies whether an ICMP Destination Unreachable message is forwarded to the source address on any IP datagram that is discarded because of security checks. Note: There is only one IP security access list per Multiprotocol Interconnect module. IP security access list may contain up to 32 entries. 3. Enable IP security on the module, using the IP System Parameters panel. 4. Specify up to two IP security lists for each IP port using the IP Port Parameters panel.
4. Configure the system-wide IPX parameters by selecting IPX System Parameters from the IPX Menu . An example of the resulting panel is shown in Figure 186 on page 309. Config * IPX System Parameters System IPX Routing: Enabled Module: BladeRunner Time: 10:52 13 Jan 95 IPX Security: Disabled Internet Bcast Handling: Enabled Exit Return to the previous screen Figure 186.
Config * Log. Port: 1 IPX Port Parameters LOGICAL PORT Module: BladeRunner Time: 11:00 13 Jan 95 IPX Port Routing: Enabled Host Number: 08008F4001A0 Disposition: discard Network Number: 00000001 Interface Delay: 1 Encapsulation: ieee802.3 RIP Timer: 30 SAP Timer: 60 Security Access List 1: 0 Search Port Security Access List 2: 0 Prev Port Next Port Exit Return to the previous screen Figure 187.
• Interface Delay This data This best is the estimated time taken for an IPX packet containing 576 bytes of to traverse the hop between the interface and the associated link. parameter is displayed in milliseconds and is used to determine the route to a destination address. If there are more than one route with different interface delay, the one with the lowest value will be the best route. If the interface delay between two or more routes is the same, the one advertised first will be selected.
Allows you to display information about the physical ports currently installed on your module. • Physical Port Protocol Statistics Displays different statistical information for each port, depending on the type of the interface and the link protocol configured for the port. • Physical Interface Statistics This screen is applicable to the WAN ports only. • Logical Port Statistics Screen Displays statistical information about the packets sent and received on a logical port.
Displays information about various link state advertisements sent and received by the Multiprotocol Interconnect module. • OSPF Link State Database Table Displays the link state database in the Multiprotocol Interconnect module. This information includes the area and the router identifier from which the link-state advertisements were received. • OSPF Virtual Neighbor Table Displays all the virtual neighbors.
314 8260 Multiprotocol Intelligent Switching Hub
Appendix A. Power Requirements for 8250/8260 Modules A.1 Power Requirements for 8250 Ethernet Modules Table 41.
A.2 Power Requirements for 8250 Token-Ring Modules Table 42. Power Requirements for 8250 Token-Ring Modules Module Feature Code Type Description # of Slots Used Power Consumption (watts by voltage type) +5 +12 -12 -5 -2 MAU 3820T Token Ring 8 ports 8-pin RI/RO One 7 0 0 0 0 Twisted Pair Media 3821T Token Ring 20 ports 8-pin Two 12 0 0 0 0 Fiber Repeater 3822TR Token Ring ST connec. 8-pin RI/RO One 11 0 0 0 0 T R M M Basic 3823 Token Ring Mgmt.
A.4 Power Requirements for 8250 Internetworking Modules Table 44. Power Requirements for 8250 FDDI Modules Module Feature Code Type Description # of Slots Used Power Consumption (watts by voltage type) +5 +12 -12 -5 -2 Ethernet B r i d g e 3828EB Ethernet 2 ports Two 20 7.5 .25 0 0 Token Ring Bridge 3883TB Token Ring 2 ports SR bridge One 14 0 0 0 0 Token Ring Bridge 3958 Token Ring 2 ports SR/SRT bridge One 14 0 0 0 0 Ethernet Intercon.
318 8260 Multiprotocol Intelligent Switching Hub
Index Numerics 18-Port Active Module Switching Module 180 Configuration 180 18-Port Active Per-Port Switching Module 174 address-to-port-mapping 174 automatic speed detection 174 backplane segments 174 beacon recovey 174 cabling 174 configuration 177 DIP switches 176 DIP switches meaning 177 DPLL 174 fan-out device support 174 front view 175 isolated segments 174 JADC support 175 LED Descriptions 175 RI/RO trunks 174 ring speed 174 RJ-45 connectors 174 side view 176 simultaneous segments 174 STP support 174
Address-to-Port-Mapping (continued) support for MAC-less stations 163, 166 Alarm Group 199 analog collision detection 19 Statistics Collection 19 applying power 8250 modules 84, 85 8260 modules 82 ATM Control Point and Switch module 2 auxiliary port pinout 42 RS-232 support 40 RS-423 support 40 B Backplane Signalling for TR Segments Beacon Bit Streaming state 210 Errors 210 Event 203, 208 Frame Streaming state 210 Isolating error 131 MAC frame 131 Packet 204, 208 packets 202 Ring Signal Loss state 210 Send
Distributed Management Module (DMM) DMM front panel 39 DMM alert_filter 57 DMM alerts 57 authentication 57 change 57 hello 57 DMM Command DMM community table 56 DMM Configuration changing password 44 Clear Community 57 Clear IP 55 configuring terminal settings 47 configuring users 44 defining new Superuser 45 displaying current users 45, 46 Save Device 54 Set Alert Console_Display 57 Set Clock 50 Set Community 56 Set Device 51 Set Terminal Console 47 Set Terminal Prompt 49 Set Terminal Timeout 50 Show Commu
E-MAC Configuration (continued) Set Module Monitor_Contention Set Module Network 65, 68 Show Module 65, 68 E-MAC Monitoring Functions 213 RFC 1271 213 RMON MIB 213 Eavesdropping Protection 123 EC-DMM 58 front panel 58 installetion 59 jumpers 59 LCD display 60 LED description 60 Enhanced TriChannel 3, 13 supported LAN segments 13 Error Abo rt 205 Address Copied 205 beacon 131 Burst 204 Collision 198, 199 Congestion 205 CRC Align Error 98, 197, 199 Fragment 199 Fragments 198 Frame-Copied 205 Frequency 206 Hos
Ethernet 24-Port 10BASE-T Module (continued) Security Card support 99 side view 102 simultaneous segments 99 Telco-type connector 99 usage 104 UTP backbone 99 Ethernet 40-Port 10Base-T module 9 Ethernet LAN Overview 97 802.
Intelligent Power Management (continued) Vital Product Data (VPD) 29 Intelligent Power Subsystem 6 Intrusion protection 122 diasbling ports 121 jamming ports 121 reporting intruders 121 IP Addressing for DMM 38 IPX J Jitter Attenuator Daughter Card 10 Jitter Attenuator Daughter Card (JADC) DPLL 141 140, 141 L LAN Segments on the Backplane 13 Lobe test 145 Local Management System (LMS) 247 Boothelper Parameters menu 287 Bridge menu 261 Bridging System Parameters menu 262 Configuration menu 251 Conversion
Multiprotocol Interconnect Module (continued) processor 240 programming power requirements 243 RIP implementation 245 Router Engine Module (REM) 240 routing functions 244 SNMP support 240, 250 software download 240 source address filtering 274 source route transparent bridging 244 translational bridging 244 transparent bridging 244 power management Considerations (continued) overload situation 86 power budget 85 power failure 85 Power Management Scenarios 86, 87, 88 A power-supply failure - scenario 1 86 A
RMON Support (continued) using T-MAC 230 S Security Address Table autolearning 121 entries 121 manual procedure 121 size 121 Serial Control Interface (SCI) 27 Serial Line Interface (SLIP) default gateway 49 IP address 49 IP subnet mask 49 Short History SHOW COUNTER Command for Ethernet segments 215 for token-ring segments 222 ShuntBus 14 LAN segments supported 14 Signal Flow on the Token-Ring Modules SNMP management 2 Software Download in-band 240 out-of-band 240 Speed Detection 148 Static Switch 145 148
Token-Ring Network Parameters (continued) ring speed 173 splitter support 174 token-ring path 19 token-ring pins on the Enhanced TriChannel 19 clock-in 19 clock-out 19 data-in 19 data-out 19 token-ring pins on the ShuntBus 21 clock receive 21 clock transmit 21 data A transmit 21 data B transmit 21 token-ring segments on the backplane 19 Token-Ring Surrogate Functions Configuration Report Server 214 Ring Error Monitor 214 TR 18 Port Active Module Switching Module 9 TR 18 Port Active PPS Switch Module 9 TR 20
ITSO Technical Bulletin Evaluation RED000 International Technical Support Organization 8260 Multiprotocol Intelligent Switching Hub May 1995 Publication No. GG24-4370-00 Your feedback is very important to help us maintain the quality of ITSO Bulletins. Please fill out this questionnaire and return it using one of the following methods: • • • • Mail it to the address on the back (postage paid in U.S.
ITSO Technical Bulletin Evaluation GG24-4370-00 Fold and Tape RED000 Please do not staple IBML Cut or Fold Along Line Fold and Tape NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK POSTAGE WILL BE PAID BY ADDRESSEE IBM International Technical Support Organization Department 545, Building 657 P.O.
IBML Printed in U.S.A.
