Related Manuals for Black Box Series 500
Summary of Contents for Black Box Series 500
-
Page 1: Reference Manual
Series 500 Frame Relay/Leased Line Bridge/Router Reference Manual LR1530A-R3, LR1530A-EU-R3, LR1531A-R2, LR1535A-R2 5500100-10 equivalent to 5500087-10 © Copyright 2002 by Black Box Corporation. - Page 2 Introduction Ethernet Remote Bridge/Router The Ethernet remote bridge/router provides IP and IPX routing combined with a protocol transparent bridge. This bridge/router combination is often the best solution to linking remotely located LANs where most of the traffic is IP or IPX with smaller amounts of traffic from other protocols such as NetBIOS or DEC LAT.
-
Page 3: Arp-Address Resolution Protocol
Introduction ARP—Address Resolution Protocol A protocol called ARP (Address Resolution Protocol) is used to determine the MAC address of a particular IP address. The MAC (Medium Access Control) address is unique predefined number for each device on the LAN. The manufacturer of the device assigns MAC addresses. -
Page 4: Ip Header Details
Introduction • Local router will look in its ARP cache to find the MAC address of the destination router as determined by the IP address in the routing table. • Local router will rebuild the complete frame with a new MAC header indicating the MAC address of the destination router. -
Page 5: Time To Live
Introduction Time to live The time to live section is used to prevent a frame from traversing the network forever. This field contains a number (maximum 255) that is set when the frame is originally generated. Each time the frame is passed through the bridge/router, the bridge/router will decrement the time to live by two. -
Page 6: Icmp Messages
Introduction Time Stamps The time stamp option is used to record the time at which the IP frame passed through each router on its way to the destination station. ICMP Messages Internet Control Message Protocol (ICMP) messages are used to perform station and router protocol participation. ICMP messages are passed between routers, or between routers and stations. -
Page 7: Rip-Routing Information Protocol
Introduction RIP—Routing Information Protocol The most important function of the IP protocol is routing. IP routers constantly exchange information keeping their routing tables up to date. A method of communication is required to ensure compatibility between all IP routers in the network. RIP is the portion of the IP protocol that is used for router communication. -
Page 8: Ipx Addressing
Introduction IPX Routing and The Ethernet Remote Bridge/Router The Ethernet bridge/router may be used to route between IPX networks. Novell Netware uses a suite of protocols for LAN communications. The Novell protocols include IPX, SPX, RIP, SAP, plus others, and operate at layers 3 and above. These protocols, their relationship with each other, and the general operation of a Novell network are discussed in this section. - Page 9 Introduction Network Addresses The Network Number addresses the network. All stations on the same “network” will have the same Network Number. Note that a network could be a single segment, or multiple segments joined by either bridges or repeaters. In IPX internetworks, routers must be used to join different networks together. Node Addresses The Node Number identifies the individual stations in a Network.
-
Page 10: Establishing An Ipx Connection
Introduction The checksum is a hold-over field from the XNS model used by Novell. In the original XNS header, the checksum was used; however, Novell decided that the MAC trailer CRC was enough protection and the IPX header checksum need not be used. Therefore the IPX checksum is permanently set to FFFF. The length field indicates the total length of the IPX packet. -
Page 11: Routing Information Protocol
Introduction When a Client or Server notices that a Server from its known Server list has missed a broadcast (it should get one about every 30 seconds), it starts up a counter, and when the Server has missed 3 broadcast intervals (about 180 seconds) that Service is removed from the known Server list. -
Page 12: Rip/X Broadcasts
Introduction RIP/X Broadcasts A RIP broadcast is sent out by IPX routers every 30 seconds or so. Each broadcast may contain information on up to 15 different routes (to 15 different networks). If a router knows of more than 15 networks it will send out two (or more) broadcasts. -
Page 13: The Initial Bridging Process
Introduction Bridging and the Ethernet Remote Bridge/Router The bridge portion of the Ethernet remote bridge/router is an Ethernet Media Access Control (MAC) level bridge providing an efficient means of interconnecting IEEE 802.3 Local Area Networks supporting a choice of standard Ethernet (10Base5), Thin Ethernet (10Base2) and Twisted Pair (10BaseT) interfaces. -
Page 14: Local Destination Addresses
Introduction The bridge/router captures each frame and looks at the source address contained within the Ethernet frame. Since the bridge/router knows which LAN segment the frame was received from, it can determine that this station must be located on this segment. As a result, it has just learned the location of the station. This process will continue for the period defined by the Forwarding Delay option, and in this fashion the first stage of the LAN address table is built. -
Page 15: Aging Timer
Introduction Aging Timer During the bridging process, the filter table is built giving the location (bridge port or LAN segment) of known Ethernet addresses. The table would become quite large, eventually reducing performance, if stations were added, removed, or moved without the old information being purged periodically. -
Page 16: Link Compression
Introduction Ethernet Bridge/Router Feature Definitions Telnet A Telnet LAN station or another Ethernet bridge/router has the ability to connect to the Operator Interface of any Ethernet bridge/router supporting the Telnet feature. With the Telnet feature, all Ethernet bridge/routers on a network may be managed from a single point. - Page 17 Introduction Compression Ratio File Type Figure 1 - 5 Typical Compression Ratios by File Type Data compression will give a 56/64 Kbps link an effective throughput range from 112/128 Kbps when transferring binary files, to 364/384 Kbps when transferring graphic files. This increased throughput significantly reduces the bandwidth required between the LANs to achieve a given performance level, and also allows the use of lower-cost transmission facilities.
-
Page 18: Operating Software Upgrades
Introduction Operating Software Upgrades The Ethernet Bridge/Router includes flash memory, that allows new system code to be downloaded using the Trivial File Transfer Protocol (TFTP). This allows software updates to be performed quickly and painlessly from a host server (with TFTP capabilities) on the network. -
Page 19: Universal Wan Module
Link Interface Reference Pinout Information The router is manufactured with four different WAN link modules: V.35, LXT411 CSU/DSU, Universal WAN or T1/E1. The type installed may be determined from the label on the WAN link output connector. V.35 Module: The V.35 link interface is provided as a DB25 connector on the back of the bridge/router, so an interface converter is needed to convert to the standard V.35 connectors. -
Page 20: Console Connector
Link Interfaces Reference Changing the link speed within the menu system of the router changes the clock output speed that is generated on the DTE Terminal Timing pins on the link interfaces. Console Connector The console connector on the router is a DCE interface on a RJ45 pinout. The supplied DB9 to RJ45 converter should be used to connect to the DB9 connector of a DTE terminal. - Page 21 Link Interfaces Reference The LXT411 CSU/DSU link connection is set to operate at 64 Kbps by default. The link may be set to 56 Kbps via the software menus if required. When two CSU/DSU link routers are to be connected via a leased line in a back to back set-up, the unit must be set to 56 Kbps link speed and a null-modem crossover cable used for the connection.
-
Page 22: Link Pinouts
Link Interfaces Reference V.35 Link Pinouts The connector shown here and pinouts described here correspond to the connector labeled “V.35” on the back of the router. DB25 Female DTE DB25 M.34 Direction Contact Contact Circuit From Number Number Name DCE DCE Protective Ground Transmitted Data (A) Received Data (A) -
Page 23: Null-Modem Cable Configuration
Link Interfaces Reference V.35 Null-Modem Cable Configuration Figure 2 - 5 V.35 Null-Modem Cable The connecting cable must be a shielded cable. Circuits which are paired (contain an (A) and (B) reference) should be connected to twisted pairs within the connecting cable. -
Page 24: Rs232C Link Pinouts
Link Interfaces Reference V.24 & RS232C Link Pinouts The pinouts described here correspond to the RS232/ V.24 mode for a Universal WAN router. DB25 Female DTE CCITT Direction Contact Circuit Circuit From Number Number Circuit Name DCE DCE Protective Ground Transmitted Data Received Data Request to Send... -
Page 25: X.21 Link Pinouts
Link Interfaces Reference V.11 & X.21 Link Pinouts The pinouts described here correspond to the V.11/X.21 mode for a Universal WAN router. Note: A DB25 to DB15 pin converter will be required to connect to V.11/X.21 service. X.21 Direction Contact Circuits Circuit From... - Page 26 Link Interfaces Reference RS442 & RS530 Link Pinouts The pinouts described here correspond to RS530 mode for a Universal WAN router. Direction Contact Circuit From Number Circuit Name DCE DCE Shield Protective Ground BA (A) Transmitted Data BB (A) Received Data CA (A) Request to Send CB (A)
-
Page 27: Rs232 Null-Modem Cable Configuration
Link Interfaces Reference RS232 Null-Modem Cable Configuration Figure 2 - 9 RS232 Null-Modem Cable The connecting cable must be a shielded cable. This cable is needed when it is necessary to connect two units back-to-back and a set of modems is not available. Note that this cable specifies DB25 connectors on each end to allow direct connection to the link interface connector on each unit. -
Page 28: Rs530 Null-Modem Cable Configuration
Link Interfaces Reference RS530 Null-Modem Cable Configuration DB25 MALE DB25 MALE Shield Shield Received Data (A) Transmitted Data (A) Received Data (B) Transmitted Data (B) Transmitted Data (A) Received Data (A) Transmitted Data (B) Received Data (B) Request To Send (A) DCE Ready (A) DCE Ready (B) Request To Send (B) - Page 29 Link Interfaces Reference V.11/X.21 Null-Modem Cable Configuration Figure 2 - 11 V.11/X.21 Null-Modem Cable The connecting cable must be a shielded cable. Circuits which are paired (contain an (A) and (B) reference) should be connected to twisted pairs within the connecting cable.
-
Page 30: Wan Link Control-Signal Operation
Link Interfaces Reference WAN Link Control-Signal Operation CTS flow control is not supported. 1) When a call is made to the bridge/router, RI will be asserted by the modem. The bridge/router responds by driving DTR and RTS high to signal to the partner’s modem that it is ready to establish communications. The bridge/router then waits (for the duration of the CD Wait Time, default 60 seconds) for the partner’s modem to respond with incoming CD and DSR signals driven high. -
Page 31: Event Logs
Event Logs The Ethernet bridge/router generates event logs for various functions performed by the bridge/router. All of the event logs are stored in the internal event log file, which is accessible through the Network Events menu. Certain event logs are classified as alarms because they are deemed to be of higher urgency. Alarm logs are indicated by an asterisk (“*”) at the start of the alarm text and are printed on the ALARM line on the menu system as well as being stored in the event log. - Page 32 Event Logs DHCP: pool deleted due to mismatch with new IP address Generated when the address of this device is changed , rendering the block of addresses assigned to the DHCP pool invalid. DHCP: Requested address unavailable <IP address> Generated when the address requested by a client is unavailable DHCP services –...
- Page 33 Event Logs IPX: X, unknown SAP packet type received Generated when the device receives an invalid SAP packet. IPX: X, demand RIP failed Generated when this device reaches the end of the attempts to negotiate demand RIP for the IPXCP connection.
- Page 34 Event Logs Link X CSU/DSU: Connected Generated when the CSU/DSU link module has established a connection to the remote partner CSU/DSU. Link X CSU/DSU: Initialized Generated when the CSU/DSU link module has completed initialization and has established communications with the router. Link X CSU/DSU: Line ERROR Generated when the CSU/DSU link module is in an unknown error state.
- Page 35 Event Logs LMI discarding STATUS on link X – Enquiries not started Generated when the bridge/router discards a Status message received from the frame relay network on a link that the bridge/router has not yet started the Local Management Interface. No NCP's open, tearing link down Generated when a PPP link does not have a Network Control Protocol operating.
- Page 36 Event Logs Starting IPCP negotiation with <remote site alias> Generated when the Internet Protocol Control Protocol negotiation has been initiated with the remote site device associated with the stated remote site profile. Starting IPXCP negotiation with <remote site alias> Generated when the Internet Packet Exchange Control Protocol negotiation has been initiated with the remote site device associated with the stated remote site profile.
-
Page 37: Alarm Logs
Event Logs Alarm logs: * Auto-learning of LMI type on link X unsuccessful Generated when the LMI type on a link is not successfully auto-learned. * Bad internal block checksum detected Generated when power up diagnostics finds a fault in the internal block of the EEPROM. * Closing remote site X (call limit) Generated when the specified number of calls has been exceeded. - Page 38 Event Logs * Closing remote site X (resumption failure) Generated due to failure to resume a suspended connection. * Closing remote site X (scheduled down) Generated due to time-of-day schedule deactivation of the connection. * Closing remote site X (suspension timeout) Generated due to reaching maximum time that the connection may be suspended.
- Page 39 Event Logs * Download aborted – Incomplete file Generated when a TFTP download is aborted before the file transfer is complete * Download aborted – Invalid FCS Generated when there is a checksum failure after a file download. * Download aborted – Incompatable boot code Generated when the operating code file downloaded is incopatible with the boot code in this device.
- Page 40 Event Logs * FTP server added to firewall The IP address of the FTP server added to the table of services available through the firewall. * FTP server removed from firewall The IP address of the FTP server removed from the table of services available through the firewall. * IP protocol parameters initialized Generated when IP protocol communications to a remote site configured for frame relay are negotiated successfully.
- Page 41 Event Logs * Link X, DLCI Y attached to remote site <remote site alias> Generated for frame relay applications when a connection has been made for the DLCI associated with the remote site alias. * Link X down Generated when a WAN link goes down. * Link X down to <remote site alias>...
- Page 42 Event Logs * NAT table full Generated when no more ports are available for Network Address Translation. * No available remote site for learned DLCI Generated when, during Frame Relay Auto-learning, the remote site table is filled, no space is available to create another entry.
- Page 43 Event Logs * Remote Site <remote site alias> still closing Generated when a connection is attempted to a remote site whose link is still in the process of being disconnected. * Remote site <remote site alias> suspended Generated when the connection to the specified remote site has been suspended. * Remote site <remote site alias>...
- Page 44 Event Logs * (T1/E1) Yellow Alarm Off Yellow Carrier Failure Alarm is being turned off – alarm cleared when Yellow Alarm indicator signal from far end stops. * Telnet server removed from firewall The IP address of the Telnet server removed from the table of services available through the firewall. * Telnet server added to firewall The IP address of the Telnet server added to the table of services available through the firewall.
- Page 45 Event Logs * Unable to route!! UDP failure Generated when the device tried to open an already open UDP channel, causing IP routing to fail. * Unknown call type on remote site <remote site alias> The attempted call is not a Frame Relay or PPP leased line call. Possible cause is a remote site profile being deleted while a connection attempt is being made.
- Page 46 Event Logs PPP security logs: CHAP authentication failure so terminate link. Generated when the CHAP authentication sent by this router in response to a request from a remote site is rejected. CHAP failed for <remote site alias> Generated when the remote site router failed a CHAP authentication request from this router. The remote site name is displayed if known.
-
Page 47: Programmable Filtering
Programmable Filtering Programmable filtering gives the network manager the ability to control under what conditions Ethernet frames are forwarded across bridge or bridge/router ports. There are many reasons why this might need to be accomplished, some of which are security, protocol discrimination, bandwidth conservation, and general restrictions. To reach a specific filtering goal, there is usually more than one possible filter expression that may be used. - Page 48 Programmable Filtering Security—“Filter if Destination” Filter if Destination is a function that allows you to filter an Ethernet frame based on the destination of its address. If the destination address equals the address that the Filter if Destination function has been applied to, the frame is filtered.
- Page 49 Programmable Filtering Security—“Filter if Source” Filter if Source is a function that allows you to filter an Ethernet frame if the source address of the frame equals the address that the Filter if Source function has been applied to. Example: Assume that a Personal Computer is located on segment 1 on the local bridge/router.
- Page 50 Programmable Filtering The bridge/router will prompt you for the LAN that the station is located on; enter the name of the partner bridge/router LAN (LAN345678, for example). Note that the Status of the address is marked as [present], the location is updated to LAN345678 and the Permanent entry is [enabled].
- Page 51 Programmable Filtering From the MAC ADDRESS FILTERS MENU, make sure that the Filter Operation is currently set to “negative”. This will cause the MAC Address Filters specified to be used for forwarding frames with the specified MAC addresses. From the MAC ADDRESS FILTERS MENU, enter a 1. This will place you at the first EDIT MAC ADDRESS FILTER MENU screen.
- Page 52 Programmable Filtering From the CONFIGURATION MENU, enter an 8. This will place you at the FILTER SET-UP MENU, where access to the individual filtering menus is obtained. From the FILTER SET-UP MENU, enter a 1. This will place you at the MAC ADDRESS FILTERS MENU, where access to the MAC Address filters is obtained.
-
Page 53: Pattern Filter Operators
Programmable Filtering Pattern Filter Operators The following operators are used in creating Pattern filters and will be discussed further in the following pages. For additional information refer to the octet locations diagrams at the back of this manual. Each octet location may contain a HEX value. offset Used in pattern filters to determine the starting position to start the pattern checking. -
Page 54: Bridge Pattern Filtering
Programmable Filtering Bridge Pattern Filtering Protocol Discrimination Protocol discrimination may be required to prevent or limit the protocols that may traverse a bridged Local Area Network. In Local Area Networks there may be many different Network and Transport layer protocols that coexist on the same physical media. -
Page 55: Transport Control Protocol / Internet Protocol (Tcp/Ip)
Programmable Filtering IP, and no more This example performs just the opposite function to the above example. Only IP packets will be allowed to be passed across the bridged network. For this function there must be a method to prevent all but IP packets from being filtered. For this the NOT (“~”) logical operator is used. -
Page 56: Local Area Transport (Lat)
Programmable Filtering Local Area Transport (LAT) The Local Area Transport (LAT) protocol is used exclusively by DEC for terminal access between DEC hosts and terminal servers located on an Ethernet network. This example is similar to the Internet Protocol example described previously. The protocol type field value that is used for LAT frames is equal to 6004. -
Page 57: Bandwidth Conservation
Programmable Filtering DEC uses protocol types 6000 to 600F, and although some are undefined, a simple filter mask can be created to filter all DEC traffic. Filter all DEC The mask to filter all DEC traffic would be: 12-600X The X is a variable representing the last four bits (a nibble) of the type. This will effectively filter all Ethernet frames that contain a protocol type of 6000 through to 600F. -
Page 58: General Restrictions
Programmable Filtering General Restrictions Bridge Filter Masks may be created to generally restrict access for various purposes. Some of these purposes may be to filter specific combinations of information. This section will generally depict masks that may be created to control traffic across the bridged LAN network. -
Page 59: Mask Combinations
Programmable Filtering Mask Combinations Mask combinations may be required to ensure that a frame is sufficiently qualified before the decision to filter is made. The qualification a frame must go through before a filter decision is made depends on the reason for the filter. Nonetheless, a few examples below have been provided that should aid in the creation of a mask that may require that extra little bit of qualification. -
Page 60: Ip Router Pattern Filtering
Programmable Filtering IP Router Pattern Filtering Pattern filtering may be used on any portion of the IP frame. IP pattern filtering behaves the same as bridge pattern filtering, except the start of the IP frame is offset 0, because the IP router function of the bridge/router handles only the IP frame itself. -
Page 61: Octet Locations On A Bridged Tcp/Ip Frame
Frame Formats This appendix provides octet locations for the various portions of three of the common Ethernet frames. When creating pattern filters these diagrams will assist in the correct definition of the patterns. The offset numbers are indicated by the numbers above the frame representations. -
Page 62: Ethernet Type Codes
Frame Formats ETHERNET TYPE CODES Type Code Description 0800 DOD IP 0801 X.75 Internet 0804 Chaosnet 0805 X.25 Level 3 0806 0807 XNS Compatibility 6001 DEC MOP Dump/Load 6002 DEC MOP Remote Console 6003 DEC DECNET Phase IV Route 6004 DEC LAT 6005 DEC Diagnostic Protocol... - Page 63 Frame Formats Octet Locations on an IPX Routed Novell Netware Frame Octet Locations on a Bridged XNS Frame 5500100-10...