Page 1 USER’S GUIDE FastNET ATX NMS PORT SEGMENT OFFLINE RING 1 RING 2 RX ST RX ST OFFLINE TX 16 TX 16 SEGMENT 1 SEGMENT 2 SEGMENT 3 OFFLINE FDDI MIC A OPTICAL BYPASS FDDI MIC B OFFLINE MULTI-MODE MULTI-MODE O F F L I N E...
Page 3: Fcc Notice
Notice NOTICE Cabletron Systems reserves the right to make changes in speciﬁcations and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made. The hardware, ﬁrmware, or software described in this manual is subject to change without notice.
Page 4 Notice DOC NOTICE This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications. Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la class A prescrites dans le Règlement sur le brouillage radioélectrique édicté...
Page 5 EXCLUSION OF WARRANTY AND DISCLAIMER OF LIABILITY EXCLUSION OF WARRANTY. Except as may be specifically provided by Cabletron in writing, Cabletron makes no warranty, expressed or implied, concerning the Program (including its documentation and media). CABLETRON DISCLAIMS ALL WARRANTIES, OTHER THAN THOSE SUPPLIED TO YOU BY CABLETRON IN WRITING, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE PROGRAM, THE...
Page 6: Declaration Of Conformity
Notice DECLARATION OF CONFORMITY Application of Council Directive(s): Manufacturer’s Address: European Representative Name: European Representative Address: Conformance to Directive(s)/Product Standards: Equipment Type/Environment: We the undersigned, hereby declare, under our sole responsibility, that the equipment packaged with this notice conforms to the above directives. Manufacturer Mr.
Page 7: Table Of Contents
1.5 ATX ARCHITECTURE ...1-6 1.6 ATX FEATURES ...1-6 1.6.1 Netbios Name Caching ...1-8 1.6.2 ATX Local and Remote Port Mirroring...1-9 1.6.3 IPX with Token Ring Source Routing ...1-10 1.6.4 Event Logging on the ATX ...1-10 1.6.5 ATX LAN Switch Workgroups... 1-11 1.6.6 ATX Packet Processing Engine...
Page 8 1.10.1 Command Syntax Conventions ...1-40 1.10.2 Basic LCM Commands...1-41 CHAPTER 2 INSTALLING AND CONNECTING TO THE NETWORK 2.1 ATX FRONT PANEL ...2-1 2.2 MOUNTING THE ATX ...2-3 2.3 CONNECTING THE POWER SUPPLY...2-4 2.3.1 Checking the Power-up Sequence ...2-5 Power-up Diagnostics Sequence...2-6 Troubleshooting the Power-up Sequence ...2-7...
Page 9 3.2.11 Disabling Routing Functions...3-12 3.3 CONFIGURING IPX ROUTING...3-12 3.3.1 Assigning an IPX Address ...3-13 3.3.2 Displaying IPX Addresses ...3-13 3.3.3 Enabling IPX Routing Functions ...3-14 3.3.4 Displaying IPX Routing Functions...3-15 3.3.5 Disabling IPX Routing...3-15 3.4 CONFIGURING APPLETALK ROUTING...3-15 3.4.1 Enabling AppleTalk Routing...3-16 3.4.2 Displaying AppleTalk Routing Functions...3-16 3.4.3 Disabling AppleTalk Routing...3-17 3.4.4 Assigning a Network Number...3-17...
Page 10 3.15.3 eventdisplay...3-42 3.16 CONFIGURING SOURCE ROUTE TRANSLATIONAL BRIDGING (RIF CACHING) ...3-42 3.16.1 Managing SRTB ...3-43 3.16.2 SRTB Usage in the ATX ...3-44 CHAPTER 4 MONITORING AND MANAGING THE ATX 4.1 MONITORING STATISTICS...4-1 4.1.1 General Status and Statistics ...4-4 4.1.2 IP Status and Statistics...4-4 4.1.3 ICMP Status and Statistics ...4-6...
Page 11 CHAPTER 5 FILTERS 5.1 FILTERING AND PERFORMANCE CONSIDERATIONS ...5-2 5.2 USING FILTERS FOR SECURITY PURPOSES...5-2 5.3 USING FILTERS TO IMPROVE PERFORMANCE...5-3 5.4 ADDRESS TABLE FILTERS ...5-4 5.4.1 Destination Address Filter...5-5 5.4.2 Source Address Filter ...5-5 5.4.3 Combination Address Filters ...5-6 5.4.4 Source Address Multicast Filter...5-6 5.5 COMBINATION PORT FILTERS...5-7 5.5.1 Conﬁgurable Fields ...5-8...
Page 12 7.5.1 ATX Does Not Power Up ...7-9 7.5.2 Module Status LED Not Lit ...7-9 7.5.3 Connectivity Problems ...7-9 7.5.4 ATX Has Rebooted...7-10 7.5.5 ATX Does Not Respond To NMS ...7-10 CHAPTER 8 ADDING/SWAPPING MODULES AND MAINTENANCE 8.1 ADDING A MODULE...8-1...
Page 13 8.3 MAINTENANCE ...8-3 8.3.1 Power Fuse...8-3 8.3.2 Fan Filters...8-4 8.3.3 Hot Swapping the Power Supply...8-4 APPENDIX A SPECIFICATIONS FOR THE ATX APPENDIX B PACKET TRANSLATION PROCEDURE APPENDIX C NULL MODEM CABLE PINOUTS APPENDIX D GLOSSARY APPENDIX E BIG ENDIAN TO LITTLE ENDIAN CONVERSION...
Page 14 Contents...
Page 15: Chapter 1 Introduction
Related Documentation. This manual is the base of the ATX documentation set. Each module that you can use in the ATX also has its own manual. The complete documentation set is described in the section Related Documentation.
Page 16 ﬁlters using the Local Console Manager. It also provides speciﬁc examples of how ﬁlters can be used. • Chapter 6, Traps, describes the traps the ATX sends to an SNMP manager. • Chapter 7, Diagnostics and Troubleshooting, describes the ATX diagnostics and provides information on troubleshooting common problems.
Page 17: Document Conventions
Caution: A Caution alerts the reader to a specific action which may negatively affect your computer equipment, server communication with your ATX, or may cause data loss. Warning: A warning means you could cause physical harm to yourself. Follow the guidelines in the manual or on the unit itself when handling electrical equipment.
Page 18: Related Documentation
1.3 RELATED DOCUMENTATION You may need to refer to the following documentation: • ATX MIB Reference Guide – contains enterprise MIB information. • Token Ring Switch Module User Guide – contains instructions on installing the modules into the ATX and connecting your Token- Ring module to the network.
Page 19: Getting Help
• Network load and frame size at the time of trouble (if known) • The serial and revision numbers of all modules in the ATX • Module status (crash codes, if any), ﬁrmware version, any verbose display messages; to display messages, use the display verbose and status commands •...
Page 20: Atx Architecture
LAN to ATM migration. The ATX has ﬁve slots for various interface modules and space for two power supplies. The ATX front panel is shown in Figure 1-1. FastNET ATX...
Page 21 • Compilation of statistics for trafﬁc generated by each user device connected to an ATX segment. • Ping and Trace Route provide the ATX with the ability to execute (through LCM) ping and trace route commands which show router hops, IP interfaces each packet must traverse and how much time elapsed between transmit and response of a ping command.
Page 22: Netbios Name Caching
When the ATX receives any of these frames and Netbios Name Caching is enabled on the port the frame was received on, the ATX will identify the frame as a special Netbios Name Caching frame. Once identiﬁed, a couple of actions takes place. First, the ATX...
Page 23: Atx Local And Remote Port Mirroring
Local port mirroring is when the diagnostic port is on the same ATX as the mirrored ports. Remote port mirroring is when the diagnostic port is on a different or remote ATX from the mirrored ports. The mirrored ports have to be either local or remote to the diagnostic port, not both.
Page 24: Ipx With Token Ring Source Routing
Support of IPX over source routing (IPX SR) enables the ATX LAN switch to achieve this capability and route IPX packets through SR bridges. See section 3.11 IPX Routing Over Source Route Comands for additional information on source routing commands.
Page 25: Atx Packet Processing Engine
Each workgroup can be deﬁned by port, IP network address and/or IPX network number. A total of 100 virtual workgroups can be deﬁned on each ATX LAN Switch. The ATX LAN Switch can route between IP workgroups but all other workgroups will need an external router (See Workgroup to Workgroup Communication).
Page 26: Input/Output Modules
4 Segments 1.6.7 Input/output Modules The ATX has four types of modules available. The modules slide into the face of the ATX. The module installation procedures are in Chapter 8. The ATX supports the following: • 3E02-04, 3E05-04, 3E07-04, 3E08-04, and 3E02-08-ATX - Multi- segment Ethernet modules that come in ﬁve models-four UTP...
Page 27: Power Supply
When both supplies are used the load is balanced between the power supplies. 1.7 BRIDGING FUNCTIONS The basic bridging function of an ATX is to transparently forward data packets to the network segments (LANs) it interconnects. Incoming packets are stored momentarily while the ATX checks their destination addresses against the ATX's address table.
Page 28 The choice of bridging methods is determined both by end station requirements and by other internetworking equipment. Source routing end stations may use any of the ATX three bridging methods. Transparent end stations must use either transparent or SRT bridging. When in doubt, transparent bridging is the easiest to conﬁgure and use.
Page 29 FDDI port should be conﬁgured for SRT bridging. (SRT over Ethernet is not a standard, but is available for use between multiple ATX chassis in backbone applications. In this case, the “Ethernet” may actually be a microwave or satellite link with an Ethernet-like interface.)
Page 30: Transparent Bridging
(RIF) is used in source route networks to indicate the path a frame has taken through the network. This feature will enable the ATX to switch between source route only networks like Token Ring and transparent networks like Ethernet and FDDI. RIF is not supported on Ethernet networks and is seldom used on FDDI networks.
Page 31: Source Routing Bridging
Source routing bridging (SR) is an alternative to transparent or spanning tree bridging, and is widely used in Token Ring networks. The ATX supports source routing bridging on Token Ring LANs, and an enhancement to source routing called SRT on all LANs.
Page 32 Introduction Station A Bridge B Station C Ring Ring data packet address data Figure 1-3. Source Routing Example In the example in Figure 1-3, a data packet traveling from station C on LAN 43 through bridge B to station A on LAN 7 must specify the full route it is to take.
Page 33: Source Routing Transparent Bridging
(notably multicast transmission). IEEE has deﬁned SRT bridging for Token Rings, and ANSI has incorporated it into the FDDI standards. The ATX supports SRT bridging on these, as well as on Ethernet (for Ethernet, there is no such standard; the ATX provides this as a proprietary backbone service).
Page 34: Translation
E1 on Ethernet LAN 2. To reach either server, the Ethernet packet from workstation 100 is translated by ATX A to a FDDI format. To reach server E1, the packet is translated by ATX B back into Ethernet format.
Page 35: Routing Functions
IP trafic while remaining in bridging (rather than routing) mode. SNMP management stations are now able to poll the ATX locally and remotely, but this does not permit the ATX to send SNMP traps to multiple SNMP management stations.
Page 36: Ip Routing
ATX is receiving. Routing Information Protocol (RIP) RIP is one of the protocols that allows the ATX to build an accurate, current routing table. Routers, including the ATX, send out broadcasts every 30 seconds advertising the networks they know about, the routes to those networks, and the number of hops to get there.
Page 37: Reverse Address Resolution Protocol (Rarp)
Enabling the BOOTP relay option is useful in environments where you have a diskless client and its server is on a network on the other side of the ATX. When the client boots up, it sends out a broadcast requesting the software it needs to download.
Page 38: Multiple Ip Networks Per Port
Introduction 1.8.2 Multiple IP Networks Per Port The ATX’s routing software allows you to conﬁgure a single IP network to span multiple physical network segments (ATX ports). This enables you to conﬁgure multiple physical networks as one logical network. Engineering Figure 1-6.
Page 39 Logical Network A, B, and C Figure 1-7. Multiple Logical Networks On One Physical Network When assigning multiple IP network addresses to an ATX port, the port must be conﬁgured for routing. In addition, the logical networks connected to an ATX must see the ATX as a gateway(router).
Page 40: Ip Multicast Routing
• The host is participating in the router discovery protocol (ICMP). When using LCM each ATX port can be conﬁgured for zero or more IP addresses, with associated subnet masks. Each IP address deﬁnes an IP subnetwork. Each IP subnetwork is a distinct entity with respect to protocols, such as RIP (Routing Information Protocol), and is treated as a separate interface.
Page 41 A temporary host group is one that must have at least one member, a permanent host group can exist with zero members. Currently the ATX supports only temporary host groups. Note: There are no restrictions on the location or number of members assigned to a host group.
Page 42 LAN D. Similarly, an IP multicast packet destined to the group member on LAN B that originated on that LAN will not be forwarded to the other LANS. LAN A FastNET ATX PACKET PROCESSING ENGINE NMS PORT POWER OCTAL IEEE 802.3 / ETHERNET 10BASE-T...
Page 43: Ip Routing Over Source Routing
LAN A FastNET ATX NMS PORT PACKET PROCESSING ENGINE POWER OCTAL IEEE 802.3 / ETHERNET 10BASE-T SEGMENT LINK PROC OFFLINE QUAD IEEE 802.5 TOKEN RING (UTP) RING 1 RING 2 RING 3 RING 4 RX ST RX ST RX ST...
Page 44 Introduction The architecture behind source-routing bridges is that a packet header containing a route is inserted by the source end-station. For the source end-station to discover a route to a destination end- station, it must learn of a route by transmitting a special type of packet called an explorer packet.The explorer packet is duplicated by source-routing bridges as it discovers possible route choices.
Page 45 ARP is used to dynamically map IP addresses to MAC addresses. The resulting source route is kept as part of the ARP cache. The IP routing over source-routing feature allows the ATX to: • Recognize Type-6 (IEEE 802) ARP packets, as well as Type-1 (Ethernet) ARPs.
Page 46: Conﬁguring Ip Routing Over Source Routing
MIB. The sipNetToMedia Table, within the Cabletron proprietary MIB, allows you to manage the source route as part of the ARP cache. See the ATX MIB Reference Guide for information on sipckt and the sipNetToMedia Table. 1.8.6 IPX Routing The ATX can route Internetwork Packet Exchange (IPX) packets.
Page 47: Routing Information Protocol (Rip)
Introduction Routing Information Protocol (RIP) RIP is one of the protocols that allows the ATX to build an accurate, current routing table. Routers, including the ATX, send out broadcasts every 60 seconds advertising the networks they know about, the routes to those networks, and the number of hops to get to there.
Page 48: Appletalk Routing
2 protocol. The ATX stores a table of routing information it learns through Routing Table Maintenance Protocol (RTMP) packets sent out by other routers. The ATX also sends out RTMP packets to let other routers know of the routes it has learned. By storing the RTMP packets, the ATX knows where to forward packets it receives.
Page 49: How A Macintosh Learns Its Address
The router ﬁrst chooses an address in the start-up network range (ff00-fffe) so that it has an address that other routers may respond to before it learns its real network range. The ATX probes to ﬁnd its network range; it picks a network range and sends out probes to see if it can use that range.
Page 50: Seed Routers
Introduction receives a response, it knows its network range and then performs additional AARP probes to choose a host number. The router then sends RTMP requests to begin building its routing table. Next the router asks other routers for a list of zones so it can create a zone list.
Page 51: Trunking
Trunking can be used between devices which support trunking. Currently, it is possible to connect Fast Network 10s to ATXs via Ethernet connections, ATX to ATX via Ethernet, Token Ring, or FDDI connections, or Fast Network 10s to Fast Network 10s.
Page 52: Trunk Groups
Each set of connections between ATXs is called a trunk group. You can conﬁgure several trunk groups to interconnect your ATXs. Each ATX can have up to eight trunk groups. Each trunk group can include up to eight ports. For example, you could have four trunk groups of six ports each or three trunk groups of eight ports each.
Page 53: Local Console Manager
You can also use a standard SNMP-based NMS. The following sections describe LCM command syntax and the basic LCM commands for logging in and out and getting help. LCM commands used for conﬁguring your ATX are described in the conﬁguration chapters. FastNET ATX...
Page 54: Command Syntax Conventions
• To quit any command press the Control-C keys (^C or Ctrl-C). • You can abbreviate any command where there is no ambiguity; if there is ambiguity, LCM responds with an error message. For example: ATX >ex Error: ambiguous command • Commands are not case sensitive.
Page 55: Basic Lcm Commands
Return key several times to get the LCM prompt ( > Note: The LCM prompt (ATX>) does not appear on the screen immediately. Pressing the Return key repeatedly brings up the LCM prompt. RETURN is the default password.
Page 56 Introduction [clear|[overwrite|stopwhenfull][add|del][FILTERS]] eventtrap {on | off} exit or logout filters {display|modify|add|delete} help or ? ident ipaddr [PORTS {a|cl|de|di} [ADR [MSK]]] iproute [PORT-RANGE [OPTIONS]] ipxaddr [[[PORT#] NETWORK] FRAMING] ipxroute [PORT-RANGE [OPTIONS]] mirror [remote|PORT-RANGE [OPTIONS]] nbcache [PORT-RANGE [OPTIONS]] nbentries [<#entries>] nbname {display|delete}[OPTIONS] nbtimer [<age_timeout>] offline MODULE# online MODULE#...
Page 57 [PORT-RANGE [{off | transparent | sr | srt} [noBPDU]]] ATX> id Software Currently Running: Release ATX 3.3.09 12-Mar-97 Next Bootstrap (2nd bank) : Release ATX 3.3.09 12-Mar-97 Power-up test failures: none System Up Time: 3 days, 21:27:05 PPE Type: ES/1 ATX...
Page 58 PORT-RANGE sna {off | passRif | stripRif | passBoth | onewaybitswap} Usage: translate PORT-RANGE stripRif | passBoth} ES/1 ATX> workg Usage: workgroup [NAME [{delete | PORT-RANGE [INFO]}]] INFO: {all | ip IP-ADDRESS [NETMASK] | ipx [IPX-NETWORK]} ES/1 ATX> trans...
Page 59 [{arp|bootp|srArp|ipx|ipxsr|apple|none|netbios|sna|all} OPTION]] Port 2 is not configured for token ring. Port 3 is not configured for token ring. Port 4 is not configured for token ring. Port 5 is not configured for token ring. Port 6: no translations. Port 7 multimedia translations: sna passBoth Port 8 multimedia translations: arp oneto6swap...
Page 60 Introduction 1-46...
Page 61: Chapter 2 Installing And Connecting To The Network
You may want to familiarize yourself with the front panels so you are aware of what is taking place. The front panel of the ATX is shown in Figure 2-1; it also shows front panels of some module types.
Page 62 SEGMENT 4 PROC SEGMENT 1 SEGMENT 2 OFFLINE ATX LEDs and their functions are described in Table 2-1. Refer to the module documentation for a description of the LEDs for that module. Table 2-1. Meaning Of ATX LEDs POWER On – Power supply is on and the voltage is within the STATUS acceptable range.
Page 63: Mounting The Atx
2.2 MOUNTING THE ATX If the ATX is to be table-mounted, make sure it is within reach of the external power supply and the network cables to which it will be connected. Make sure you allow enough room at the front of the chassis for cable installation and access.
Page 64: Connecting The Power Supply
To connect the ATX to an external power source (100 to 120 Vac or 200 to 240 Vac at 47 to 65 Hz), follow the steps below: 1. When using one power supply, plug the power cable into the power socket labeled SUPPLY A on the back of the ATX.
Page 65: Checking The Power-Up Sequence
2.3.1 Checking the Power-up Sequence Before connecting the ATX to any other devices, power on the unit and observe the power-up diagnostics sequence to check for proper operation as described below. The power-up diagnostics sequence completes in approximately 45 seconds depending on the number and type of modules installed.
Page 66: Power-Up Diagnostics Sequence
Figure 2-3. LED Activity During Normal Operation Power-up Diagnostics Sequence To observe the power-up sequence completely, you may want to repeat it. To restart the power-up sequence, turn the power switch off, then on again, or press the reset button above the power RING A...
Page 67: Troubleshooting The Power-Up Sequence
4. The TURBO STATUS LED will come on, followed by the STATUS or PROC LEDs of the interface modules (from the top down). 5. The LEDs will indicate that the ATX has begun proper operation, as shown in Figure 2-3. Troubleshooting the Power-up Sequence...
Page 68: Replacing The Power Supply
Replacing the Power Supply It is critical that the power supply inserted into the top slot of the ATX chassis be installed very carefully if you are installing it while the ATX is powered on. Failure to use caution while installing the...
Page 69 Figure 2-4. Chassis With Power Supply A Positioning Tabs And Supporting To replace the power supply in slot A (the top slot) 1. Turn power switch on Power Supply A (PSA) off. 2. Remove the two thumb screws holding the power supply in place.
Page 70: Connecting The Local Console Manager
The Local Console Manager is a tool for conﬁguring, monitoring, and managing the ATX through an out-of-band RS-232 connection. To connect LCM: 1. Attach a null modem at either the terminal end or the ATX port end. The null modem cable should be a female DB-25 cable. Pinout information is listed in Appendix C, Null Modem Cable Pinouts.
Page 71 3. Set the terminal to 9600 baud, 8 data bits, 1 stop bit, and no parity. 4. Press the Return key a few times. If the ATX is powered on, it will respond with its prompt LCM is now ready to use.
Page 72 Installing and Connecting to the Network 2-12...
Page 73: Chapter 3 Configuring
All ATX MIB variables are listed and described in the ATX MIB Reference Guide. This manual provides LCM commands you can use to conﬁgure your ATX. If you are using a tool other than LCM, refer to its accompanying documentation. 3.1 CONFIGURING BRIDGING A bridge is a device that makes it possible to link two or more networks together.
Page 74 Conﬁguring LAN 1 LAN 2 LAN 3 Figure 3-1. Typical Bridging Application Bridges regulate network trafﬁc on the basis of the source and destination addresses that are in each data packet. Bridges are protocol-transparent, meaning they can handle different types of trafﬁc regardless of the network protocol, for example, IP and IPX.
Page 75: Enabling Bridging Functions
3.1.1 Enabling Bridging Functions The bridging functions you can enable for the ATX include: • Transparent – End nodes take no part in routing; thus, a transparent bridge places no burden on end nodes.
Page 76: Displaying Bridging Functions
0 (zero). Note: In order to accomplish routing tasks, the ATX must be configured to recognize hexadecimal references. For instance, to route using IPX, a Novell Network Number must be used for configuration purposes.
Page 77: Disabling Bridging
LCM responds, Port 2 bridging: Off 3.2 CONFIGURING IP ROUTING The ATX is shipped from the factory without an IP address. If you are enabling IP routing, you need to assign addresses to the ports which will be performing routing functions. The LCM command for adding IP addresses is provided in the next section.
Page 78: Deleting An Ip Address
Conﬁguring • Class A addresses are used in very large networks that support many nodes. The ﬁrst byte identiﬁes the network and the other three bytes identify the node. The ﬁrst byte of a class A address must be in the range 1-126. The address 100.125.110.10 would identify node 125.110.10 on network 100.
Page 79: Changing A Subnet Mask
IP address. 3.2.4 Displaying IP Addresses The ipaddr command displays the IP addresses, subnet masks, and MAC addresses of all ports on the ATX which you are managing. 1. Type: ipaddr Table 3-1. Displaying IP Addresses...
Page 80: Enabling Ip Routing Functions
• Off – no IP routing at all. • On – IP routing, but no inter-router protocols. • RIP – IP routing, with RIP enabled, allows the ATX to send out broadcasts every 30 seconds advertising the networks it knows about, the routes to those networks, and the number of hops to get to there.
Page 81: Adding An Ip Address To A Port
Port 5 routing: IP Routing, RIP, Bootp relay Port 6 routing: IP Routing, RIP, Bootp relay 3.2.6 Adding an IP Address to a Port To add an IP address to an ATX port: Type: ipaddr <port number> add <ip address> <subnet mask> <source route operation option>...
Page 82: Deleting An Ip Address From A Port
LCM ipaddr command: • add – Allows you to add an IP address to an ATX port. • delete – Allows you to delete an IP address from an ATX port. • clearALL – Allows you to delete all IP addresses from an ATX port.
Page 83: Ip Multicast Routing Lcm Commands
To display the current IP Address Table, type with no arguments. Note: Before you may issue the clearAll command to an ATX port, IP routing must be disabled for that port. To re-enable routing for the port, an IP address must be assigned.
Page 84: Displaying Ip Routing Functions
Conﬁguring 3.2.10 Displaying IP Routing Functions To display the IP routing functions that are enabled for all ports: Type: iproute LCM responds with a list of all ports and the routing functions that are enabled. Usage: iproute [PORT-RANGE] [off] [on] [rip] [proxy] [bootp]] Port 2 routing: IP Routing, RIP Port 3 routing: IP Routing, RIP Bootp relay...
Page 85: Assigning An Ipx Address
Type: ipxaddress <port number> <new address> LCM responds by displaying the IPX address table. 3.3.2 Displaying IPX Addresses The ipxaddr command displays the IPX addresses, node ID, and framing type for all ports on the ATX which you are managing. Conﬁguring 3-13...
Page 86: Enabling Ipx Routing Functions
0x77665544 0x31265488 0x22446688 3.3.3 Enabling IPX Routing Functions The IPX routing functions you can enable for ports on the ATX may be: • Off – no IPX routing at all • On – IPX routing • SR – IPX routing over source routing...
Page 87: Displaying Ipx Routing Functions
3.3.4 Displaying IPX Routing Functions To display the IPX routing functions that are enabled for all ports: Type: ipxroute LCM responds with a list of all ports and the routing functions that are enabled. Usage: ipxroute [PORT-RANGE [{off | on | sr}]] Port 2 IPX routing: enabled Port 3 IPX routing: enabled Port 4 IPX routing: enabled...
Page 88: Enabling Appletalk Routing
Port 8 AppleTalk routing: enabled 3.4.2 Displaying AppleTalk Routing Functions You can use the atroute state for all ports on the ATX. To display the AppleTalk routing state for all ports Type: atroute LCM responds: Usage: atroute [<port range> {off |on}]...
Page 89: Disabling Appletalk Routing
Port 8 AppleTalk routing: enabled Port 21 AppleTalk routing: disabled 3.4.3 Disabling AppleTalk Routing AppleTalk routing can be disabled on a per port basis using LCM. AppleTalk packets that are received on disabled ports are discarded. To disable AppleTalk routing on a port or port range: Type: atroute <port range>...
Page 90 (Net-Cfg) and zone configuration (Zone-Cfg) status is listed as unconfigured. As soon as another device comes up, the ATX configures itself and the status is changed to configured. The configuration range (Cfg-Range) is the network number range you have assigned to this port. The active range is the network number that was seeded to your network.
Page 91: Displaying The Network Number
(Net-Cfg) and zone configuration (Zone-Cfg) status is listed as unconfigured. As soon as another device comes up, the ATX configures itself and the status is changed to configured. When the configured zone and network status is listed as garnered, it means that this port learned its network number and zone name from the seed router.
Page 92: Displaying A Zone Name
Conﬁguring Port 6 To make the zone name you are adding the designated default zone name: Type: atzone <port number> <“zone name”> on default For example, atzone 6 “Engineering” on default, would create the default zone name Engineering on port 6. LCM responds: AppleTalk Zones Port 6...
Page 93: Enabling Trunking
ATX A is handling only a small trafﬁc load. Therefore, the A to B trunk group has just two ports per ATX. ATXs B and C are expected to support a higher trafﬁc load. Therefore, the B to C group has eight ports.
Page 94: Disabling Trunking
Note: The ATX-to-ATX connections must be point-to-point. There cannot be any other devices on those LAN segments. The ports used for trunking can be in any order. However, both ends of the ATX- to-ATX connections must have trunking enabled for the ports that are being used for the connections.
Page 95: Modifying Mib Variables
NMS. This section provides a list of common MIB variables you may want to change. (Refer to the ATX MIB Reference Guide for a complete listing and description of MIB variables.) Each variable is ﬁrst described in words and is then identiﬁed in MIB form, for example, configGetPass - {config 3}.
Page 96: System Name
Conﬁguring 3.7.2 System Name The system name is a name assigned to the ATX by the network administrator. By convention, the system name is the fully qualiﬁed domain name. (This name then becomes the LCM prompt.) sysName - {system 5} DisplayString (SIZE (0..255))
Page 97: Get Password
Aging Parameter Dynamic (learned) addresses are automatically deleted from the ATX address table after a certain length of time. The aging time default is 5 minutes as set by the IEEE 802.1d standard. However, the aging parameter can be changed, using the MIB variable dot1dTpAgingTime.
Page 98: Conﬁguration Alarm Dynamic
Conﬁguring Conﬁguration Alarm Dynamic When the ATX learns a new address or ages (deletes) an old address it may or may not send a trap based on the value of this variable. conﬁgAlarmDynamic, addrAlarmMAC 3.8 CONFIGURING NETBIOS NAME CACHING The Netbios name caching function initially comes up disabled. To enable or disable name caching, the ports to enable must be provided.
Page 99: Virtual Workgroup Lcm Commands
value of the Netbios aging timer. The age-timeout argument can be modiﬁed and is interpreted in terms of seconds. This timer is the amount of time a Netbios name remains in cache without activity. The default will be the same as that for spanning tree which is 5 minutes or 300 seconds.
Page 100: Classification
ALL workgroup (see Example #1). Example #1 Deﬁned workgroups: workgroup red 3-5 ALL workgroup blue 5-6 ALL ATX LAN Switch Broadcast from A will only be seen by B and C Broadcast from B will only be seen by A and C 3-28...
Page 101: Workgroup Of Type Ip
Broadcast from C will only be seen by A, B and D Broadcast from D will only be seen by C Broadcast from E will be seen by all forwarding ports 3.10.2 Workgroup of Type IP The destination IP address within the broadcast packet is used to determine the workgroup (see Example #2).
Page 102 Conﬁguring ATX LAN Switch An ARP from: A or B destined for 100.100.1.xxx will only be seen by A, B and C A or B destined for 100.100.2.xxx will only be seen by A, B and C A or B destined for 100.100.3.xxx will only be seen by A, B and C C destined for 100.100.1.xxx will only be seen by D...
Page 103: Workgroup Of Type Ipx
C A or B destined for the 0x999 network will only be seen by A, B and C A or B destined for the 0x000 network will only be seen by A, B and C ATX LAN Switch Conﬁguring 3-31...
Page 104 E destined for the 0x999 network will stay local to E E destined for the 0x000 network will stay local to E Example #4 Deﬁned workgroups: workgroup red 3-5 all workgroup blue 5,6,7 ipx 0 workgroup green 7 ipx 0x999 3-32 ATX LAN Switch...
Page 105: Same Port In Multiple Workgroups
Conﬁguring A SAP from: A or B destined for the 0x1234 network will only be seen by A, B and C A or B destined for the 0x999 network will only be seen by A, B and C A or B destined for the 0x000 network will only be seen by A, B and C C destined for the 0x1234 network will only be seen by D and E C destined for the 0x999 network will only be seen by D and E...
Page 106: Workgroup To Workgroup Communication
3.10.5 Workgroup to Workgroup Communication This type of communication can only be achieved by routing. With the ATX LAN Switch having the ability to route IP packets, it will route between IP workgroups (See Example #5). However, the ATX LAN Switch will NOT be able to route between IPX workgroups.
Page 107: Local And Remote Port Mirroring Commands
- to turn local port mirroring off on the ports speciﬁed mirror port-range to port# oversize port-range - range of mirrored ports port# - the diagnostic port on the local ATX oversize - discard or truncate; what to do with oversized packets ATX LAN Switch Conﬁguring...
Page 108: Types Of Media And Framing
Ipaddr - ip address of the local ATX where the diagnostic port resides Note: Both ATX LAN Switch’s have to have port mirroring turned off in order to fully disable the remote port mirroring function. 3.11.1 Types of Media and Framing Mirrored and diagnostic ports have no restrictions and can be any of the ATX LAN Switch’s interfaces, Token Ring, Ethernet, Fast...
Page 109: Packet Capturing And Mirroring
On the network layer, there should be no alteration. For example, when an inbound routed packet is mirrored, the image reﬂects the packet prior to any changes made by the ATX LAN Switch routing software. The ATX LAN Switch mirror software maintains the original packet ordering of bridging frames between the inbound and outbound interfaces.
Page 110: Mirrored Filters
Conﬁguring 3.11.3 Mirrored Filters The ATX also allows you (via the existing port ﬁltering feature; (Chapter 5 in the ATX LAN Switch User’s Guide) to establish “mirror ﬁlters” which can help reduce the amount of trafﬁc seen by the diagnostic port. Using a “mirror ﬁlter,” you can restrict the amount of monitored trafﬁc by ﬁltering inbound or outbound...
Page 111: Example #2: Remote Port Mirroring
Port 5 on ATX #1 has an ip address of 134.141.100.1. Port 4 on ATX #2 has an ip address of 134.141.100.2 . (P4 has to have an ip address assigned so ATX #2 will have an ip to ARP with.) Conﬁg on...
Page 112: Ipx Routing Over Source Route Commands
Mirror Filters with REMOTE Port Mirroring: • Desired - to see packets from station A (on P2) only • Implementation - add a PMEntry ﬁlter to port 2 on ATX #2 with station A’s MAC address as the source address in the ﬁlter.
Page 113: Event Logging Commands
3.15 EVENT LOGGING COMMANDS The Event Log is established using the LCM. New LCM commands have been added in order to manage the event logging. There are 3 new LCM commands: 3.15.1 eventﬁlter The LCM command format is: eventfilter [clear | [overwrite | stopwhenfull] [add|delete][allentries ! [filter_name[,filter_name]*] ]] Examples:...
Page 114: Eventtrap
3.16 CONFIGURING SOURCE ROUTE TRANSLATIONAL BRIDGING (RIF CACHING) SRTB allows the ATX to strip and cache routing information for source route frames. Routing information (RIF) is used in source route networks to indicate the path a frame has taken through the network.
Page 115: Managing Srtb
Ethernet networks and is seldom used on FDDI networks. In order to merge source routed Token Ring networks with transparent Ethernet or FDDI networks the ATX must strip the RIF when communicating to Ethernet or FDDI and insert the RIF when communicating back to Token Ring.
Page 116: Srtb Usage In The Atx
Source Route network that it does not have a RIF entry for (default when enabled) ARE - enables the ATX to use a All Route Explorer frame when transmitting onto a Source Route network that it does not have a RIF entry for.
Page 117 SRT mode and is either the entrance or exit port. If there is a station directly attached to the ATX and it sends out a frame with a NULL RIF the ATX will not cache that station with RIF associated with it and treat it as a transparent station.
Page 118 Bridge Address Table with the RIF of Ring 2, Bridge F and Ring 1. The next time station A speaks to station B the frame will enter P1 on the ATX transparently and be sent out P2 with the RIF of Ring 1, Bridge F and Ring 2.
Page 119 SRTB all on ARE ETHERNET Station A sends out a broadcast for station B. The ATX will see that station A resides on P1 and enter station A into the Bridge Address Table with no RIF associated. The ATX will then send an ARE (Null RIF) out P2.
Page 120 Station C sends out a broadcast for station B. The frame from station C will have a Null RIF (2 bytes). Since the ATX’s P3 is conﬁgured for SR, the ATX will add Ring 2, Bridge 1 to the frame and send it out P2.
Page 121 TMS380 guide) to notify the end station that this is the maximum frame size this bridge will forward. For the ATX, this ﬁeld is selectable via SNMP and defaults to 81144 for 16MB rings and 4472 for 4Mb rings. The scenarios below...
Page 122 Reason: The ATX has no way of telling station A that it can not handle frames greater than 4500 because it is not passing trafﬁc to station A with the Routing Control ﬁeld. Station A will be able to connect to station B.
Page 123 4500 and wants to transfer a ﬁle to station D, it will not work. Reason: The ATX does have the Routing Control ﬁeld to tell station C that it can’t handle a 4500 frame size but the default for the ATX is 8144. Solution: Conﬁgure the dot1dSrPortLargestFrame OID with 4472, 2052 or...
Page 124 Conﬁguring 3-52...
Page 125: Chapter 4 Monitoring And Managing The Atx
NMS as your primary tool. Managing your ATX consists of bringing modules on or ofﬂine, disabling or enabling ports, setting the community name for the ATX, and changing the console baud rate, all of which can be done using LCM. 4.1 MONITORING STATISTICS The ATX collects statistics that can assist you to build a comprehensive proﬁle of the trafﬁc ﬂow on each network, between...
Page 126 • UDP status and statistics • SNMP status and statistics • Spanning Tree status and statistics. Note: All statistics counters are cleared when the ATX is reset. Counters for individual ports are reset when the module is disabled and then re-enabled.
Page 127 • Number of packets with CRC errors on each network. The following are the statistics collected by the ATX for each end- node: • Number of seconds since the end-node last sent a packet on the network.
Page 128: General Status And Statistics
• The number of centiseconds (hundredth of a second) since the ATX was last reset. [sysUpTime] • What the ATX is being used for: bridging, IP Routing, or Bridging and IP Routing. [sysServices] • The physical location of the ATX. [ •...
Page 129 • The total number of input packets successfully delivered to the IP user-protocol layers. [ipInDelivers] • The total number of IP output packets generated by this ATX. This count does not include any received packets forwarded by this ATX. [ipOutRequests] •...
Page 130: Icmp Status And Statistics
MIB variable that collects the statistics is provided in square brackets.) • The total number of ICMP messages which were received by this ATX. This also includes all messages received with errors. [icmpInMsgs] • The number of ICMP messages which were received with errors (bad checksums, bad length, etc.).
Page 131 • The total number of ICMP messages which were created by this ATX. This includes all messages counted by [icmpOutMsgs] • The number of ICMP messages which this ATX did not send due to problems discovered entirely within the ICMP subsystem (such as lack of buffers). [icmpOutErrors] •...
Page 132: Udp Status And Statistics
• The number of received UDP datagrams that could not be delivered for reasons other than the lack of an application at the destination port. This number is always zero, since the ATX handles resource limitations by discarding datagrams at the IP...
Page 133: Snmp Status And Statistics
• The number of SNMP PDUs received by the ATX. [snmpInPkts] • The number of SNMP PDUs created by the ATX and passed to the PPE. [snmpOutPkts] • The number of SNMP PDUs received by the ATX which had an unsupported SNMP version.
Page 134: Spanning Tree Status And Statistics
[snmpInGetNexts] • The total number of SNMP SetRequest PDUs received by the ATX, which have been processed with no errors. [snmpInSetRequests] • The total number of SNMP PDUs created by the ATX, with a value of in the PDU's tooBig •...
Page 135: Module Status And Statistics
ﬂows from those networks. Status and statistics on each end-node, recorded in the Bridge Address Table, follows: • The port through which this station is connected to the ATX (only valid for dynamically learned addresses and unique addresses for ATX's agent software).
Page 136: Trafﬁc Analysis Statistics
• The number of packets transmitted to the station. You can conﬁgure the ATX to collect extended statistics by using an SNMP Manager to set the MIB variable ppeExtendStats to one. The ATX is shipped with no extended statistics collection as the default.
Page 137: Monitoring Status
[filterPktCnts] 4.3 MONITORING STATUS You can monitor the ATX with LCM, to see its status at a glance. The LCM commands that allow the monitoring the status of the ATX are described in the sections that follow.
Page 138 • The module was physically inserted earlier, but was not activated by the ATX at the time (due to the power being off, or the procedures not being followed correctly), and you are now turning on power to the unit.
Page 139: Displaying Mac Addresses
The age will be the most recent of the following: • Time since a packet was last received from that address. • Time since the ATX last created a packet with that source address. • Time since the ATX created that address.
Page 140 Monitoring and Managing the ATX Address Type 08:00:20:02:3a:44 Learned 3 00:40:27:03:b7:21 Static 00:80:20:a2:3b:0a Other Enter <CR> to continue, Ctrl-C to exit: To display a speciﬁc address: Type: addresses display <MAC address> For example, if you typed, addresses display 02:04:06:03:2a:43, LCM would display the following...
Page 141: Displaying Manufacturing Information
ﬂash memory, the part number, revision number, and serial numbers of all of the modules. It also displays the length of time since the ATX was last rebooted. To display the manufacturing information:...
Page 142: Disabling A Port
Resetting the ATX won’t enable a port that has been disabled. Caution: If you disable the port through which you are connected to the ATX, you will not be able to communicate with the ATX. To find the port number through which you are connected, use the addresses display command with the MAC address of you device.
Page 143: Taking A Module Ofﬂine
For example, offline 6 would take module 6 ofﬂine. Caution: If you issue an offline command for the module through which you are connected to the ATX, you will not be able to communicate with the ATX. 4.4.4 Bringing a Module Online To bring a disabled module back online, use the online command.
Page 144: Setting The Baud Rate
Monitoring and Managing the ATX 4.4.5 Setting The Baud Rate You can set the baud rate for your LCM console connection. The options for baud rate include: • 1200 • 2400 • 4800 • 9600 • 19200 Note: Make sure that the baud rate you set matches the baud rate setting for the terminal you are using.
Page 145 LCM prompts you for the new community name. 4. Enter the new community name. 5. LCM prompts you to verify the new community name by retyping it. 6. Retype the new community name. Monitoring and Managing the ATX ; you must then enter the 4-21...
Page 146 Monitoring and Managing the ATX 4-22...
Page 147: Chapter 5 Filters
For some applications, ﬁltering capabilities may be so important that they are the primary reason for using a bridge. A ﬁlter is an instruction to the ATX to screen packets based on the criteria you select. All bridges by nature ﬁlter packets; they discard local trafﬁc.
Page 148: Filtering And Performance Considerations
If, for example, a ﬁlter is conﬁgured to block all trafﬁc to the port that connects LAN A to the ATX, all access to LAN A will be restricted.
Page 149: Using Filters To Improve Performance
(localized broadcast storm prevention). An example of a ﬁrewall ﬁlter is given in the section, Filtering Application Examples. Note: The ATX multicast storm protection feature may be thought of as a firewall feature, in that it performs a protective blocking function, Filters...
Page 150: Address Table Filters
The age entry indicates when a frame from the device was last received by the ATX. The source ﬁlter and multicast source ﬁlter entries are ﬂags used solely for ﬁltering; they instruct the ATX Port (segment)
Page 151: Destination Address Filter
Table 5-2. The {null} port assigned by the static entry will take precedence over the port learned by the ATX's learning algorithm. Table 5-2. Representation Of A Destination Address Filter MAC address 00:01:02:03:04:05 The effect of this ﬁlter is that packets to the speciﬁed address will...
Page 152: Combination Address Filters
Filters An example of a source address ﬁlter is shown in Table 5-3. For illustration purposes, this example uses the same format as the address table entry shown previously. The actual format used for conﬁguring ﬁlters depends on the NMS you use. Table 5-3.
Page 153: Combination Port Filters
designated MAC address will be ﬁltered. Multicast packets are those destined for more than one address (using a multicast destination address). This is useful for preventing broadcast trafﬁc from a particular station. Table 5-5. Representation Of A Source Address Multicast Filter MAC address 00:01:02:03:04:05 Because the multicast source ﬁlter ﬂag is set to ON, this ﬁlter will...
Page 154: Conﬁgurable Fields
ﬁlter). If no value is speciﬁed for a particular ﬁeld, that ﬁeld will not be used for that ﬁlter. The port ﬁeld must always be speciﬁed, since it identiﬁes which trafﬁc ﬂow the ATX is to observe for ﬁltering. If only the port is speciﬁed, the ﬁlter will screen no packets to or from that port (depending on whether it is an entry (source port ﬁlter) or an exit (destination port ﬁlter), because none...
Page 155: Type
• Pseudo – allows you to create a pseudo filter to monitor traffic patterns without discarding packets. • And/Or – allows you to combine multiple port filters using the and/or operators to create boolean ﬁlter expressions. These options are discussed in detail in the section “Combination port ﬁlter options”.
Page 156: Source Range Mask
ﬁlter type is Exit. NA is the default. Port/Group # Decimal value for the number of the port or group through which the packet entered the ATX. This is valid only if the ﬁlter type is 5-10 is the default.
Page 157: Protocol Match
Exit. NA is the default. Note: You can assign a filter to a group by entering a group number rather than a port number. You can assign a group number to specified ports using an NMS. Port group numbers start at 22. Protocol Match Either NA (not applicable), True (ﬁlter the packet if the protocol type matches), or False (ﬁlter the packet if the protocol type does...
Page 158: Field Origin
Filters Field Origin Either IP, MAC, or SR (see Field Offset below). The origin is the ﬁeld from which the offset count starts. IP is the default. Field Offset The decimal offset of the portion of the packet (as stored in canonical format) to be examined.
Page 159: Threshold
Zero is the default. Threshold Number of occurrences allowed within the speciﬁed threshold time; occurrences above this number cause an alarm to be generated. (The ATX’s MIB parameter must be configAlarmDynamic set.) Zero is the default.
Page 160: Linking Combination Port Filters
Filters • Monitoring trafﬁc patterns as an aid in determining optimum network design, usage policies, etc. • Monitoring potential security threats. • Evaluating security policies. Values: either Yes (don’t ﬁlter the packet; just count the packet for statistical purposes) or No (ﬁlter the packet if it meets the ﬁltering criteria).
Page 161 Note: If you are adding a filter to be used in conjunction with another filter and they must be ordered sequentially, use the filters display command to find the index number of the existing filter. Complete the following steps to add a ﬁlter or pseudo ﬁlter to a port.
Page 162 Filters 6. Enter the ﬁrst MAC address in the source range. 7. Enter the last MAC address in the source range. 8. Enter the source range MAC address mask. ff:ff:ff:ff:ff:ff the mask you want to use, you don’t need to enter anything. If you want to use a different mask, enter that value.
Page 163 14. Enter the protocol type to match. 15. Select whether the ﬁlter will use a ﬁeld match. NA is the default. You don’t need to enter anything if you are not using a ﬁeld match. If you are not using a ﬁeld match, go to Step 20.
Page 164: Modifying A Filter
Filters If you want the ﬁlter to have another index number, enter the value you wish to use. LCM displays the ﬁlter you have just entered and prompts you whether you want to save it. Enter y (Yes) to save the ﬁlter or n (No) to cancel it.
Page 165: Displaying A Filter
This section describes typical ﬁltering applications which illustrate how a network manager can use the unique ﬁltering abilities of the ATX to accomplish a variety of speciﬁc objectives. Speciﬁc capabilities illustrated by these application examples include: • Selectively ﬁltering network trafﬁc for security purposes.
Page 166: Filtering For Security Purposes
Workstations on one network segment (subnet) are to be restricted entirely from access to devices on an adjoining subnet. In this example there are three subnets connected by a centrally located ATX (Figure 5-1). The subnets are referred to as the Engineering, Accounting and FDDI backbones. 5-20...
Page 167 LANs (3 and 4) to access LAN 2. For simplicity sake, assume that LAN 3 and LAN 4 are connected to the ATX's ports 3 and 4, respectively. LAN 2 is connected to the ATX's port 2. Two combination port ﬁlters are used to discard any packets from...
Page 168: Example 2 - Blocking Access To Speciﬁc Stations
LANs 3 and 4 cannot interact. Example 2 — Blocking access to speciﬁc stations A company uses a ATX to connect two LAN networks (Figure 5-2). Three computers on LAN 2 (the Accounting subnetwork) contain sensitive data (stations F, G, and H). The company wishes to prevent workstations on LAN 1 (Manufacturing) from accessing data on these three computers.
Page 169 In this example, a combination port ﬁlter is conﬁgured which instructs the ATX to discard data packets whose destination address is F, G, or H. Therefore, the ATX will not pass any packets from LAN 1 to LAN 2 if the packet's destination address is F, G, or H (the addresses of the computers containing sensitive data).
Page 170 • A ﬁlter can only block (discard) packets which must cross the ATX. The ATX in the example can only ﬁlter trafﬁc that travels from LAN 1 to LAN 2 (or from LAN 2 to LAN 1). An ATX ﬁlter can prevent LAN 1 stations from accessing the sensitive-data computers on LAN 2 but cannot prevent station E from accessing these computers.
Page 171: Example 3 - Restricting Access To Authorized Users
• Source address ﬁeld: B, C, or D (LAN 1), no match • Destination address ﬁeld: F, G, and H (LAN 2), no match The No match ﬂag is used in both ﬁelds to instruct the ATX to ﬁlter FastNET ATX...
Page 172: Example 4 - Filtering By Vendor Id
(B, C, or D). Only authorized users will be able to access stations F, G, or H on LAN 2. Note that the ATX is not storing information designed to identify restricted devices or authorized or unauthorized users. Instead it is using address information (which it does store) to act on ﬁlters...
Page 173: Example 5 - Conﬁguring A Firewall Filter To Control Multicasts
Furthermore, you can prevent multicasts of packets of a particular protocol type. In this example, four LANs are interconnected by an ATX (Figure 5-4). The objective is to prevent LAN 1 from sending AppleTalk I multicasts to LANs 2 and 3, yet allow AppleTalk I multicasts from LAN 1 to LAN 4.
Page 174 Filters This ﬁlter is conﬁgured as follows: • Filter identiﬁer – port number of the port attached to LAN 4 as a destination • Filter ﬁelds – protocol type = AppleTalk I, match source LAN = LAN 1, match destination address = 01-00-00-00-00-00 with mask 01-00-00-00-00-00, match This ﬁlter will block AppleTalk multicasts (or all AppleTalk trafﬁc if the destination address ﬁeld is omitted) from LAN 1 to LANs 2...
Page 175: Chapter 6 Traps
The variable bindings portion of the trap contains the • linkUp (3) – A port has come back to life, and the ATX's local management agent has re-enabled usage of the port. The variable bindings portion of the trap contains the port.
Page 176 • enterpriseSpecific (6) – The ATX is reporting some interesting information, which is contained in the variable- bindings portion of the PDU. If the ATX has been conﬁgured to require acknowledgments to its Trap PDUs ( the SNMP Manager must acknowledge the trap, generally by issuing a GetRequest for the signiﬁcant variables involved in...
Page 177: Atx Unique Trap Ids
6.2 ATX UNIQUE TRAP IDS The ATX possesses unique trap IDs which allow a SNMP Manager (Spectrum Element Manager, Spectrum) to have more control over SNMP Traps. Each trap is given a unique Trap ID, which gives detailed information about the trap and why it was sent. This also gives you the ability to select the traps you want generated and the traps you want to suppress.
Page 178 Traps • trunkState (10) - A trunking state change transition has occurred. The possible transitions are: • CLOSED - ONEWAY • ONEWAY - PERTURBED • PERTURBED - JOINED • JOINED - HELDDOWN • CLOSED - HELDDOWN • ONEWAY - HELDDOWN •...
Page 179 Traps topChangeEnd (20) - The spanning tree topology has stopped changing. ifErrors (21) - Sent whenever the number of hardware errors in received and transmitted packets has exceeded the port's limit. stRootID (22) - The spanning tree root bridge ID for the unit has changed.
Page 180 Traps fddimibSMTCFState (200) - Sent whenever the FDDI port's CFM state has changed.The fddimibPORTMACIndicated (one or two instances, depending upon whether the FDDI connection is a SAS or a DAS) is also included. fddimibMACUpstreamNbr (201) - Sent whenever the FDDI port's upstream neighbor has changed.
Page 181 Traps sfddiOBSFuseBad (212) - Sent whenever the fuse to the FDDI port's optical bypass becomes bad, or switches from bad to good. sfddiStationState (213) - Sent whenever the FDDI port's Station State has changed. swanActualSpeed (214) - The actual line speed of the WAN port has changed.
Page 182 Traps eePromReconfig (230) - The unit's EEPROM has been reconﬁgured. maxNextHop (231) - Maximum number of next hops reached. ripBadNet (232) - RIP received with wrong local network number. routeAgeOut (233) - Route aged out. sipxSAPAgeOut (234) - IPX service aged out. ipUnknownDest (235) - IP packet to unknown destination received by host.
Page 184 Traps 6-10...
Page 185: Chapter 7 Diagnostics And Troubleshooting
The ATX incorporates several built-in diagnostic and testing capabilities which are convenient to use and cause minimal or no disruption to the operational network. These capabilities are effective for isolating problems within the ATX. Built-in diagnostic capabilities include: • System-wide power-up diagnostics, which are run every time the system is powered up or reset.
Page 186: Power-Up Led Sequence
All diagnostics software is stored in nonvolatile memory (EPROM). 7.2.1 Power-up LED Sequence When you power up your ATX, the following occurs: 1. All LEDS turn on brieﬂy (this does not apply to all 10 Mbps Ethernet models, refer to the individual modules Users Guide).
Page 187: Speciﬁc Power-Up Tests
4. The TURBO STATUS LED will come on, followed by the STATUS or PROC LEDs of the interface modules (from the top down). 5. The LEDs will indicate that the ATX has begun proper operation, as shown in Figure 7-1. 7.2.2 Speciﬁc Power-up Tests The power-up diagnostic tests performed on the PPE are: •...
Page 188: Software Checksum Comparison
The operational parameters of the ATX software are also protected by a checksum comparison. When the ATX reboots, if the operational parameters of the ATX fail a checksum test due to a power failure in the midst of a previous update, the ATX will automatically use its backup version of the parameters.
Page 189: Failure Indicators
These results are passed to the NMS when the power-up diagnostics are completed (assuming the ATX is operational). The results sent to the NMS indicate which component has failed. 7.3 DIAGNOSTICS WHILE ATX IS OPERATIONAL...
Page 190: Diagnostic Results
During normal operation, the status of each LED (off, on, or ﬂashing) should be as shown in Figure 7-1. The meaning of the ATX base unit LEDs is explained in Table 7-1. The meaning of the module LEDs are explained in the individual module manuals.
Page 191 On – Power supply B is generating sufﬁcient voltage for the ATX to operate. Off – Power supply B is not present, switched off, or malfunctioning. On – Indicator that this ATX has a 1.6 Gbps backplane.
Page 192: Troubleshooting
10BASE2 or AUI Figure 7-1. LED Activity During Normal Operation 7.5 TROUBLESHOOTING This section lists several problem situations that could be encountered while using the ATX and suggests appropriate action. RING A RING B (16 LED ON if set for 16Mbps ring speed)
Page 193: Atx Does Not Power Up
7.5.1 ATX Does Not Power Up If your ATX does not power up, check each one of the following; if it still doesn’t power up, contact Cabletron Systems Technical Support.
Page 194: Atx Has Rebooted
IP addresses of the ATX. • Make sure UTP Transceivers are not pre-10BASE-T. • DEC Broadband AUI Transceiver is not supported by the ATX. • Unix spray command loses packets if workstations are busy. • RESET button is depressed in an effort to reset the module. The RESET button merely takes the module ofﬂine.
Page 195 • Check that a pathway to the ATX exists (intermediate bridges and routers are functioning). • Verify ATX’s IP addresses, one at a time using LCM. • Verify values of configNMSAddress, configAnyPass, and/or configGetPass Diagnostics and Troubleshooting 7-11...
Page 196 Diagnostics and Troubleshooting 7-12...
Page 197: Chapter 8 Adding/Swapping Modules And Maintenance
Install the additional interface module in any vacant interface slot. Caution: Observe all Electrostatic Discharge (ESD) precautions before handling the ATX. Failure to do so could result in damage to the ATX and other associated components. 8.1 ADDING A MODULE...
Page 198: Swapping A Module
To hot swap an interface module, complete these steps: 1. Take the ATX ofﬂine by pressing the OFFLINE button, use the LCM to take the ATX ofﬂine, or use an NMS to disable the module. 2. Loosen the screws at each end of the front panel of the...
Page 199: Maintenance
8. Bring the module online using LCM or an NMS if you took it ofﬂine using LCM or an NMS. 8.3 MAINTENANCE You may need to check the fuse in your ATX or to clean the ﬁlters on the fan. Those procedures are described in the sections that follow.
Page 200: Fan Filters
8.3.2 Fan Filters Each ATX comes equipped with three fans located in the back of the unit. The screens covering these fans need to be cleaned on an annual basis to prevent overheating. You don’t need to remove the fans or screens to clean them.
Page 201 Figure 8-1. Chassis With Power Supply A Positioning Tabs And Supporting To replace the power supply in slot A (the top slot): 1. Turn power switch on Power Supply A (PSA) off. 2. Remove the two thumb screws holding the power supply in place.
Page 202 The power supply should be placed as shown by the dotted line rectangle in Figure 8-2. 5. Tighten the two screws that hold the power supply into the chassis. 6. Turn the PSA power switch on Figure 8-2. ATX With Power Supply A Position Indicated...
Page 203: Appendix A Specifications For The Atx
SPECIFICATIONS FOR THE ATX A.1 PACKET PROCESSING ENGINE Dual AMD 29000 RISC processors 4 MB FLASH memory 8 MB main memory 2 MB shared memory 128 KB conﬁguration memory 1.6 Gbps internal bandwidth A.2 STANDARDS COMPLIANCE A.2.1 Protocols • ANSI FDDI X3T9.5 (SMT 7.3/MAC-2) •...
Page 204 Speciﬁcations For The ATX A.2.3 Local Routing • IP Routing (RIP) • AppleTalk Routing • IPX Routing (RIP, SAP, Diagnostic) • IP Multicast Support (DVMRP) A.2.4 Interfaces • EIA • RS-232C A.3 PHYSICAL (BASE UNIT) Height Width Depth Weight Installation options A.4 PHYSICAL (POWER SUPPLY)
Page 205 A.9 DIAGNOSTIC LEDS (BASE UNIT) Power status Engine status Turbo status Power supply A Speciﬁcations For The ATX Auto-ranging from 100 to 120 or 200 to 240 Vac 47 to 65 Hz 380 W 4 amps – 100 to 120 Vac 2 amps –...
Page 206 Speciﬁcations For The ATX Power supply B Reset A.10 SOFTWARE LOADING FLASH memory via TFTP A.11 ADDRESS TABLE SIZE 8,192 dynamic (learned) entries default, expandable to 16,384 A.12 CERTIFICATION Safety Emission Immunity UL 1950, CSA C22.2 950, EN 60950, and IEC 950 FCC Part 15 Class A, EN 55022 Class A, and VCCI Class I.
Page 207: Appendix B Packet Translation Procedure
PACKET TRANSLATION PROCEDURE Since the ATX is a multi-media unit, packets are converted from the different media into a standard canonical format. The Offset ﬁeld for the filters command refers to the canonical format packet. The exact translation procedure is deﬁned by RFC 1188 and RFC 1042, except for the encapsulation of Ethernet AppleTalk packets which uses Protocol ID of 00-00-F8 instead of all zeros.
Page 208 Packet Translation Procedure dsap ssap control protocol ID data or frame type more data more data Figure B-2. Canonical Packet Format DA (big endian) SA (big endian)
Page 209 Packet Translation Procedure header total length service type version length identiﬁcation ﬂags fragment offset protocol checksum source IP address Ethernet Frame destination IP address padding IP options (if any)... (if necessary) Figure B-3. IP Header (After Canonical Packet Format) UDP source port UDP destination port UDP checksum UDP message length...
Page 210 Packet Translation Procedure destination port source port sequence number acknowledgment number header reserved plus window length code bits padding options (if any)... (if necessary) Figure B-5. TCP Header (After IP Header)
Page 211: Null Modem Cable Pinouts
NULL MODEM CABLE PINOUTS To connect LCM you need to insert a null modem cable at either the terminal end or the ATX port end. The null modem cable can be either a female DB25 or DB9 straight-through serial cable.
Page 212 Null Modem Cable Pinouts...
Page 213 APPENDIX D GLOSSARY 4B/5B Primary data encoding scheme used for FDDI. AARP (AppleTalk Address Resolution Protocol) AppleTalk ARP performs network address to datalink address mapping on Ethernet, Token Ring, and FDDI ports. This facility is similar to IP ARP with the additional capability to probe for active addresses as described in the address acquisition section.
Page 214 Glossary agent Network management software that runs within a managed network device. alarm See trap. ANSI American National Standards Institute – One of several organizations that establishes standards which apply to internetworking and bridging. address resolution protocol – An auxiliary protocol of the IP layer used to perform dynamic address translation between MAC addresses and internet addresses.
Page 215 Glossary attenuation The amount of power (or light) lost as power travels through a medium, from the transmitter to the receiver. Difference between transmitted and received power, in decibels (dB). AUI (attachment unit interface) A standard connector type used for Ethernet connections. backbone The major, central transmission path for a network.
Page 216 Glossary BPDU (bridge protocol data unit) A data unit transmitted as part of the IEEE 802.1d Spanning Tree Protocol. The exchange of BPDUs allows bridges within a network to logically conﬁgure the network as a single spanning tree. bps (bits per second) The basic unit of data communications rate measurement.
Page 217 Glossary combination port ﬁlter A ﬁlter which may include several conﬁgurable ﬁelds and may be used to ﬁlter bridge trafﬁc in a very speciﬁc manner. concentrator A device that provides attachment points for stations that are not connected directly to an FDDI dual ring. The concentrator is connected directly to the network;...
Page 218 Glossary DAS (dual attachment station) An FDDI station connected to both the primary and secondary rings. data link layer Layer 2 in the OSI model. Deﬁnes frame construction, addressing, error detection and other services to higher layers. datagram Abbreviated and connectionless single-packet message sent from one station to another.
Page 219 Glossary downstream from another station if it receives the token or data after the other station receives the token or data. dual homing A method of connecting concentrators and stations that permits an alternate or backup path to the dual ring in case the primary connection fails.
Page 220 An active element within an Open Systems Interconnection (OSI) network layer or sublayer. Ethernet input/output module The ATX component which accepts and sends data packets to and from a connected Ethernet network. extended LAN A collection of LANs interconnected by protocol-independent bridges.
Page 221 Glossary ﬁltering rate A measure (in packets per second) of a bridge's efﬁciency in examining each frame, comparing it with an address table, and then deciding whether to discard the frame or forward it. forwarding rate The rate (in packets per second) at which a bridge can receive a stream of packets from one network segment, complete all processing, and transmit the packets to another network segment.
Page 222 Glossary ICMP (Internet control message protocol) An auxiliary protocol of IP used to convey advice and error messages about events in the IP layer. IEEE (Institute of Electrical and Electronic Engineers) International professional society which issues networking and other standards. The IEEE created the 802 family of LAN standards.
Page 223 The ability of equipment from multiple vendors to exchange information using standardized protocols. input-output module ATX component which accepts and sends data packets to and from a connected network. Input-output modules include the Ethernet modules, the FDDI modules and the Token Ring concentrator...
Page 224 Glossary module. See input-output module. IP (Internet protocol) IP is the basic datagram protocol used at the network layer of the TCP/IP stack. ISO (International Standards Organization) An organization that creates, controls and publishes standards. jitter Clocking deviation on a network. Kbps (kilobits per second) 1,000 bits per second.
Page 225 Glossary LLC (logical link control) A part of the data link layer of the OSI model that deﬁnes the transmission of a frame of data between two stations (with no intermediate switching nodes). LMA (local management agent) Software running on a network device to control the device in terms of network management functions.
Page 226 1 million bits per second. MIB (management information base) A collection of objects unique to a speciﬁc device that can be accessed via a network management protocol. The ATX has its own MIB. MIC (media interface connector) Optical ﬁber connector type used for ATX bridge FDDI port. A MIC consists of two parts: the MIC plug, which terminates the optical ﬁber cable, and the MIC receptacle on the FDDI node or...
Page 227 4B/5B encoding. (Same as NRZM, nonreturn to zero-mark.) OBS (optical bypass switch) A switch that uses an optical mechanism to automatically bypass a malfunctioning or powered-off station on an FDDI network. Prevents unnecessary ring initialization. optical receiver A circuit that converts an incoming optical signal to an electrical signal.
Page 228 (FCS). packet processing engine module High-performance component of the ATX bridge capable of performing packet analysis/transfer at a high rate. PDU (protocol data unit) The portion of a datagram that contains the data associated with a particular protocol.
Page 229 Glossary requirements and the encoding of data for transmission. physical layer Layer 1 of the OSI model. Deﬁnes and handles the electrical and physical connections between systems. PMD (Physical Layer Medium Dependent) FDDI standard that deﬁnes the medium and protocols used to transfer symbols between physical layer protocols.
Page 230 Glossary protocol suite A group of protocols related to a common framework. RARP (reverse address resolution protocol) A protocol that translates MAC addresses to IP addresses. ring A network of stations that uses a circular logical topology. Data is passed from station to station, for examination or copying, and is ﬁnally returned to the originating station, which removes the data it transmitted from the network.
Page 231 Glossary network and master (M) ports for the attachment of stations or other concentrators. SAS (single attachment station) An FDDI station that uses only one connection (an S port) for connection to the FDDI ring. segment When two or more networks are interconnected to form an internetwork, the original networks are referred to as segments.
Page 232 Glossary opposed to those automatically “learned” by the bridge). STP (spanning tree protocol) A protocol which ensures that only one path will be used between two devices; prevents active loops (multiple paths to devices) by closing certain paths. With STP operating, a redundant link serves as a backup link only if a normal path fails.
Page 233 Glossary transmit. token ring Local area network access mechanism and topology in which a supervisory frame (the token) is passed from station to station. Stations wishing to gain access to the network wait for the token to arrive before transmitting data. topology The arrangement of devices and cables that make up a network.
Page 234 Glossary TTRT (target token rotation time) A time deﬁned for tokens to travel around an FDDI ring; used to synchronize the clocking of trafﬁc on the ring. UDP (user datagram protocol) A TCP/IP protocol for the connectionless transport layer. upstream Refers to the relative position of a station in a ring or network to another station in the same ring or network.
Page 235 Glossary groups must consist of ports with all the same underlying link type. WAN (wide area network) A communication network that spans a large geographic area. ZIP (Zone Information Protocol) In the AppleTalk routing protocol, ZIP is used to disseminate zone information from routers to end nodes and between routers.
Page 236 Glossary D-24...
Page 237 BIG ENDIAN TO LITTLE ENDIAN CONVERSION The chart below provides the bit swap values and a conversion formula. Table E-1. Big Endian To Little Endian Conversion Chart Big Endian Big Endian bits value The conversion process has two steps, ﬁrst you swap the bits, then you use the conversion chart above to convert the swapped bits to the little endian format.
Page 238 Big Endian To Little Endian Conversion 1. First, swap the big endian bits, use the conversion chart to ﬁnd the equivalent values. For example: 00 00 F6 09 47 88 00 00 6F 90 74 88 2. Now that you have the bits swapped, use the conversion chart to ﬁnd the equivalent values.
Page 239 INDEX adding filters 5-15 IP addresses 3-6 IPX addresses 3-13 address classes, IP 3-5 Address Resolution Protocol. See address table filters about 5-4 combination address 5-6 destination address 5-5 source address 5-5 source address multicast 5-6 addresses adding IP 3-6 IPX 3-13 changing, IPX 3-13 deleting...
Page 240 Index bridging functions 3-5 IP routing 3-12 IPX routing 3-15 ports 4-18 displaying baud rate 4-20 bridge functions 3-4 ES/1 status 4-13 filters 5-19 IP addresses 3-7 IP routing functions 3-12 IPX addresses 3-13 IPX routing functions 3-15 MAC addresses 4-15 manufacturing information 4-17 enabling bridging functions 3-3...
Page 241 connecting 2-10 description of 1-39 LCM command syntax 1-40 LED sequence normal operation 7-6 power-up 7-2 LEDs, front panel meaning 2-2 Local Console Manager. See LCM 1-39 loopback tests 7-5 MAC addresses, displaying 4-15 manufacturing information, displaying 4-17 MIB variables, modifying 3-23 modifying filters 5-18 MIB variables 3-23...
Page 242 Index Service Advertising Protocol. See set password, defined 3-24 setting baud rate 4-20 statistics, monitoring 4-1 status, displaying ES/1 4-13 LED 7-6 stopping modules 4-19 subnet mask, IP, changing 3-7 swapping modules 8-2 switches, front panel, meaning 2-3 syntax, LCM command 1-40 system contact, defined 3-23 system location, defined 3-24 system name, defined 3-24...

Cabletron Systems ATX User Manual

Chapter 1 Introduction

Chapter 2 Installing and Connecting to the Network

Chapter 3 Configuring

Chapter 4 Monitoring and Managing the Atx

Chapter 5 Filters

Chapter 6 Traps

Chapter 7 Diagnostics and Troubleshooting

Chapter 8 Adding/Swapping Modules and Maintenance

Appendix A Specifications for the Atx

Appendix B Packet Translation Procedure

Quick Links

Troubleshooting

Related Manuals for Cabletron Systems ATX

Summary of Contents for Cabletron Systems ATX