1. Manuals
  2. Brands
  3. Develcon Electronics Manuals
  4. Network Router
  5. DI-1135
  6. Reference manual

Develcon Electronics DI-1135 Reference Manual

Ethernet bridge/router
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Orbitor 3000
Ethernet Bridge/Router
Reference Manual
Issue 2
All Software Versions
© copyright 1996 by Develcon Electronics Ltd.
7/96
Part # 168-18806

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DI-1135 and is the answer not in the manual?

Questions and answers

Related Manuals for Develcon Electronics DI-1135

Summary of Contents for Develcon Electronics DI-1135

  • Page 1 Orbitor 3000 Ethernet Bridge/Router Reference Manual Issue 2 All Software Versions © copyright 1996 by Develcon Electronics Ltd. 7/96 Part # 168-18806...

  • Page 2: Table Of Contents

    SECTION 1 — INTRODUCTION ...1-1 RBITOR THERNET EMOTE IP R OUTING AND THE RBITOR THERNET ARP—Address Resolution Protocol... 1-2 Proxy ARP ... 1-2 The Complete IP Connection ... 1-2 IP Header Details... 1-3 Protocol... 1-4 Time to live ... 1-4 Header Checksum...
  • Page 3 Filled Address Table... 1-14 RBITOR THERNET RIDGE OUTER Telnet ... 1-15 Link Compression... 1-15 WAN Topologies... 1-17 Point-to-Point ... 1-17 Multipoint ... 1-17 Bandwidth On Demand... 1-17 Disaster Recovery... 1-18 Time of Day Connect Application ... 1-18 Point-to-Point... 1-18 Multipoint ... 1-19 Disaster Recovery Backup Link ...
  • Page 4 RS530 To RS449 Conversion Cable ... 3-10 WAN L ONTROL IGNAL PERATION APPENDIX A — EVENT LOGS... A-1 APPENDIX B — PROGRAMMABLE FILTERING ... B-1 MAC A ...B-1 DDRESS ILTERING Security ...B-1 Security—“Filter if Destination”...B-2 Security—“Filter if Source”...B-3 Security—“Forward if Destination” ...B-4 Security—“Forward if Source”...

  • Page 5: Section 1 - Introduction

    LAN interface, which receives all LAN traffic and then decides where individual frames should be sent: to the IP router, to the IPX router, to the bridge, to the management system, or discarded altogether. After the LAN interface there are several functional units including the IP router, the IPX router, the bridge, and the management system.

  • Page 6: Arp-Address Resolution Protocol

    IP address being requested. The router will look in its routing table and see if it has an entry for that IP network address. If the router has an entry, the router will generate an ARP reply to send back to the originating station. The ARP reply will specify the MAC address of the router as the MAC address to send frames to for the IP address of the destination station.

  • Page 7: Ip Header Details

    IP address. Local router will look in its routing table to find the IP address of the router to send the IP frame to next. The local router will see that the destination router is the next router.

  • Page 8: Protocol

    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. 1-4 — Orbitor 3000 Reference Manual...

  • Page 9: Icmp Messages

    Because the routers share routing tables, each router has the ability to determine whether it is the best router to use for network traffic. Once a station receives a redirect, all future IP frames destined for the particular destination network will be sent to the new router.

  • Page 10: Rip-Routing Information Protocol

    When a router receives an IP frame, the router will examine it to determine the destination network address. The router will then look in the routing table, determine the next router to send the IP frame to, and send the frame to that router.

  • Page 11: Ipx Routing And The Orbitor Ethernet Remote Bridge/Router

    MAC address. An example of this is a computer acting as an IPX File Server, an IPX Router, and an IP Router. In this case the port would have a MAC address, an IPX address for its IPX functions, and an IP address for the IP Routing functions.

  • Page 12: Node Addresses

    Introduction Node Addresses The Node Number identifies the individual stations in a Network. In IPX devices, this address is assigned automatically and is identical to the MAC address. This means that the Node Number is self-configuring, and will be unique within the Network because the MAC address that was copied is (supposed to be) unique. The use of the MAC address as the Node Number allows IPX stations to be self-configuring.

  • Page 13: Establishing An Ipx Connection

    The Packet Type indicates what type of service is using the packet. Some common packet types include type 1, RIP; type 2, Echo; type 4, IPX; and type 17, Netware Core Protocol. Establishing an IPX Connection The Netware model is Client/Server, where Clients initiate calls to Servers for various purposes. The Clients are made aware of the presence of Servers by listening for Service Advertisement Protocol (SAP) broadcasts.

  • Page 14: Sap Requests

    When a router comes on line, the extent of its route tables will be its explicit route. In the case of a local router, it will be a route between the two networks to which the router is connected. In a pair of remote routers linked via a WAN connection, the first RIP broadcasts will contain only the route to the remote network.

  • Page 15: Rip/X Requests

    The hop count is the secondary measure of the length of a route; it is exactly the same as the IP hop count. If a route goes through 1 router (the shortest route), it will have a hop count of 1. If a route goes through 6 routers, the hop count for that route will be 6.

  • Page 16: The Initial Bridging Process

    These rules define what actions are taken under particular situations. One of the more important rules employed by the Orbitor Ethernet bridge/router is also a very fundamental part of the bridging process. This rule dictates how Ethernet Station Addresses are processed by the bridge. The process is outlined...

  • Page 17: Forwarding Unknown Destination Addresses

    Each time a particular address is looked up or added to the table, a timer flag is set for the “fresh” entry. When a time interval, defined by the Bridge/Router Manager expires, the address table is scanned and any “stale”...

  • Page 18: Filled Address Table

    A table is reserved for permanent address entries, separate from the table that is used for those non-permanent entries that are subject to aging. These tables may be displayed and modified with the bridge/router options discussed in this manual. Access is made locally from each Bridge/Router Console or one bridge/router can be made Master, able to control all functions of a partner Orbitor Ethernet bridge/router.

  • Page 19: Orbitor Ethernet Bridge/Router Feature Definitions

    To implement the Telnet feature, each bridge/router requires an IP address (see the Internet Set-Up Menu). It is advisable to assign an IP address to each Orbitor Ethernet bridge/router in your network that you wish to use to make Telnet connections.
  • Page 20 Introduction Compression Ratio 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 21: Wan Topologies

    The Time of Day connect feature may be used in a Multipoint configuration to provide specific hours of access. Bandwidth On Demand Each Orbitor Ethernet bridge/router has the ability to automatically enable or disable a second link based on traffic activity, time of day, or main link failure.

  • Page 22: Disaster Recovery

    One Orbitor Ethernet bridge/router will be installed at each office, and the link from each bridge/router will be connected to a dial modem. Set the link operation of the bridge/router at the head office to Conditional, and then enter a time schedule by using the Time Schedule option of the Link Activation Conditions Menu. The modem connected to the head-office bridge/router will have an autodial number of the modem at the remote office.

  • Page 23: Multipoint

    Ethernet bridge/router at the remote office locations will connect to a separate link on the Orbitor Ethernet bridge/router at the head office. The link from each bridge/router will be connected to a dial modem. Set the link operation of both links on the bridge/router at the head office to Conditional, and then enter a time schedule for each link by using the Time Schedule option of the Link Activation Conditions Menu.

  • Page 24: Section 2 - Isdn Connection Management

    During the periods of ISDN call disconnection (suspension), each end of the LAN connection must believe that the complete connection still exists. The generation of the regular status inquiries and responses normally generated by the two devices involved in the LAN connection is performed by the Orbitor ISDN bridge/router while the ISDN call is suspended.

  • Page 25: Auto-Call (Time-Of-Day Connections)

    ISDN Connection Management Auto-Call (Time-of-Day Connections) An Auto-Call connection is an ISDN connection that is established each time the Orbitor attempts to start the link. This starting of the links occurs each time an Orbitor powers up or the link goes through a restart. An Auto-Call connection would be used for a static WAN configuration that needs to be maintained at all times between sites.

  • Page 26: Address Connect

    Address Connect An Address Connect connection is an ISDN connection that is established to a specific destination Orbitor dependent upon the destination network address contained within traffic received from the local LAN. When a device on the local LAN wishes to establish a session with a device on a remote LAN, the local device will send a frame with a destination address of the remote device.

  • Page 27: Combination

    ISDN Connection Management Combination A combination of the Address Connect and Auto-Call options may be configured when a semi-permanent connection is required to one remote site and a dynamic connection is required to multiple sites. A dynamic connection indicates that the remote site for the second ISDN call will change depending upon what destination IP address is required for the connection.

  • Page 28: Protocol Awareness

    IP and IPX Client-Server sessions are established between devices located on the LANs that are routed by the Orbitor Bridge/Router. If the Orbitor is to manage the ISDN calls between the routed LANs, the Orbitors on each WAN end of the Client-Server session must be aware of the session and also must become actively involved in the maintenance of the session.

  • Page 29: Idle Timer

    ISDN Connection Management Idle Timer In order to determine the criteria for suspending an ISDN call, an Idle Timer is defined. The Idle Timer defines the period of time that LAN traffic is monitored to determine when the ISDN call will be put in suspension and disconnected.

  • Page 30: Termination Process

    Termination Process When the Orbitor has determined that there are no sessions active on an ISDN call, the Orbitor will attempt to close the call. If the partner Orbitor still has sessions assigned to that call, the call will be maintained until each side has determined that there are no active sessions using the call.

  • Page 31: Ipx Specifics

    ISDN Connection Management IPX Specifics RIP/IPX and SAP/IPX Orbitor ISDN routers incorporate a 3 second settling time for IPX RIP and SAP updates. This means that an Orbitor will wait for three seconds after an initial change in the network is reported before transmitting that change on to the remaining Orbitor routers connected on the Wide Area Network.

  • Page 32: Section 3 - Link Interfaces Reference

    Each link interface available is described with detailed information on pin designation. Standard interface cables will provide correct connections to modems, datasets, or DSU/CSUs. V.35 links are provided as DB25 connectors on the back of the bridge/router, so an interface converter is needed to convert to the standard V.35 connectors.

  • Page 33: Console Pinouts

    Link Interfaces Reference When connecting two bridge/routers back-to-back with CSU/DSU link modules, a null-modem cable is required to crossover the pins on the links. Crossing over the pins allows two bridge/routers both configured as DTE interfaces to be connected together. A DSU/CSU crossover cable would be constructed as follows: 1 -->...

  • Page 34: V.24 & Rs232C Link Pinouts

    The connector shown here and pinouts described here correspond to the connector labeled “RS232/ V.24” on the back of the Orbitor 3000. CCITT Contact Circuit Number Number Circuit 108.2 The connecting cable must be a shielded cable. NOTE For U.K. Approval: The connecting cable should be manufactured from Belden Cable, or a cable with equivalent specifications.

  • Page 35: V.11 & X.21 Link Pinouts

    Link Interfaces Reference The connector shown here and pinouts described here correspond to the connector labeled “V.11/X.21” on the back of the Orbitor 3000. X.21 Contact Circuits Number Reference T (A) C (A) R (A) I (A) S (A) Ground T (B) C (B) R (B)

  • Page 36: Rs442 & Rs530 Link Pinouts

    The connector shown here and pinouts described here correspond to the connector labeled “RS530” on the back of the Orbitor 3000. Contact Number Circuit Shield BA (A) BB (A) CA (A) CB (A) CC (A) CF (A) DD (B) CF (B) DA (B) DB (B) CB (B)

  • Page 37: V.35 Link Pinouts

    Link Interfaces Reference The connector shown here and pinouts described here correspond to the connector labeled “V.35” on the back of the Orbitor 3000. DB25 M.34 CCITT Contact Contact Circuit Number Number Number 108.2 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 38: Rs232 Null-Modem Cable Configuration

    Link Interfaces Reference RS232 Null-Modem Cable Configuration Figure 3—8 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.

  • Page 39: V.35 Null-Modem Cable Configuration

    Link Interfaces Reference DB25 MALE Protective GND Transmitted Data (A) Transmitted Data (B) Received Data (A) Received Data (B) Transmitter Signal Element Timing (A) Transmitter Signal Element Timing (B) Receiver Signal Element Timing (A) Receiver Signal Element Timing (B) Transmitter Signal Element Timing (A) Transmitter Signal Element Timing (B) Data Terminal Ready Data Channel Received Line Signal Detector (CD)

  • Page 40: Rs530 Null-Modem Cable Configuration

    DB25 MALE Shield Transmitted Data (A) Transmitted Data (B) Received Data (A) Received Data (B) Request To Send (A) Request To Send (B) Clear To Send (A) Clear To Send (B) DCE Ready (A) DCE Ready (B) DTE Ready (A) DTE Ready (B) Signal Ground Received Line Signal Detector (A)

  • Page 41: Rs530 To Rs449 Conversion Cable

    Link Interfaces Reference DB25 MALE 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. This cable is used to connect an RS530 link to an RS449 device. The cable converts from a DB25 connector to a DB37 connector.

  • Page 42: Wan Link Control-Signal Operation

    4) If the link is up, and CD is subsequently interrupted for a period of 10 seconds, then the bridge/router assumes the signal is lost and will display an Alarm. As stated previously, if the level 2 protocols can continue to send, they will be allowed to do so.

  • Page 43: Appendix A - Event Logs

    The Orbitor 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, that is accessible through the Network Events menu. Certain event logs are classified as alarms because they are not informational events. 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...

  • Page 44: Event Logs

    Generated when the bridge/router attempts a Telnet connection. bridge/router is specified. Disabling link X Generated after detection of two “multipoint” links connected to the same partner bridge/router. The bridge/router with the lower MAC address prints this event. “X” identifies the disabled link. Disconnect from X (no answer) Generated when a Telnet connection is not established because of lack of response from the target bridge/router.
  • Page 45 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 CSU telco loopback started Generated when the telco has initiated a CSU loopback to this CSU/DSU link module Link X - CSU/DSU CSU telco loopback ended Generated when the telco has terminated the CSU loopback to this CSU/DSU link module Link X - CSU/DSU DSU telco loopback started...
  • Page 46 Generated if the T1 timer is less than twice the time to transmit the largest possible frame. Multipoint links to same remote partner Generated after detection of two “multipoint” links connected to the same partner bridge/router. Network resynchronization Generated when compression resynchronization has been completed.
  • Page 47 MAC address prints this event. Password timer has expired Generated when a bridge/router has issued the password prompt for a Telnet connection and timed out waiting for the password to be supplied. PVC X status enquiry unacknowledged.
  • Page 48 Event Logs Running in BOOT mode Generated when the bridge/router is starting in Boot mode. This is the mode for software upgrades. Once the software upgrade has been successfully completed, the bridge/router restarts in Operational mode. Running in OPERATIONAL mode Generated when the bridge/router is starting in Operational mode.
  • Page 49 TFTP: stop putting filename to WWW.XXX.YYY.ZZZ The bridge/router has sent the final data packet of a file (filename), but has timed out before receiving the final ACK. The session may or may not have succeeded in delivering the entire file.
  • Page 50 Generated when the activation attempt has failed. * Activation In Progress (NT) Generated when the bridge/router initiates the activation of the module and circuit. * Activation In Progress (LT) Generated when the central office initiates the activation of the module and circuit.
  • Page 51 Code Circuit out of order No circuit/channel available Destination unattainable Out of order Degraded service Network out of order Transit delay range cannot be achieved Throughput range cannot be achieved Temporary failure Switching equipment congestion Access information discarded Requested circuit/channel not available Preemption Precedence call blocked Resources unavailable, unspecified...
  • Page 52 * Entering Maint ILMT Mode Generated when the central office invokes an Insertion Loss Measurement Test command. During the test mode the module is not available for use by the bridge/router. This test is as per the ANSI specification in ANSI T1.601-1992.
  • Page 53 IP address as this bridge/router, or another device on this network is spoofing IP using the same IP address as this bridge/router.
  • Page 54 Event Logs * IPX Routing is disabled Generated when IPX routing is disabled. This may be because operator command or an invalid configuration between WAN interconnected devices. * IPX Routing is enabled Generated when IPX routing is enabled because WAN interconnected devices have compatible IPX configurations.
  • Page 55 * Mixture of IP network and subnet addresses on WAN Generated when this bridge/router detects the existence of both IP network addresses and subnets on the WAN interconnected bridge/routers. The bridge/router may not be used to route between an IP network and an IP sub-network.
  • Page 56 “T1” times “N2” interval. * TFTP: Abort. ACK timeout Aborted a TFTP session because the bridge/router did not receive an ACK for the last data packet it sent within the TFTP “T1” times “N2” interval. * TFTP: Abort. Error (#) received Aborted a TFTP session because of the reception of a TFTP error message from the connected device.
  • Page 57 Link X CHAP failed to complete (Y) Generated when the remote site PPP router sent a CHAP challenge and this Orbitor sent a response, but no further information was received from the remote site router. The ISDN number (Y) is displayed if know.

  • Page 58: Appendix B - 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.

  • Page 59: Security-"Filter If Destination

    If the destination address equals the address that the Filter if Destination function has been applied to, the frame is filtered. Example: Assume that a host Computer is located on LAN segment 2 located on a partner bridge/router with an Ethernet address of: 00-00-01-02-03-04 Since each station on a LAN has a unique Ethernet address, this address uniquely identifies this host computer.

  • Page 60: Security-"Filter If Source

    [not present] and is of [unknown] location. In this example, the bridge/router is not aware of this station as of yet. The station has probably not been active for the bridge/router to “learn” any information about it.

  • Page 61: Security-"Forward If Destination

    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 62: Security-"Forward If Source

    When a frame of information is seen on the local LAN that contains the address of the host system in the destination field of the frame, the bridge/router will forward it. All other frames seen on the local LAN that are destined for the remote LAN will be filtered.
  • Page 63 When a frame of information is seen on the local LAN that contains the address of the Personal Computer in the source field of the frame, the bridge/router will forward it. All other frames seen on the local LAN that are destined for the remote LAN will be filtered.

  • Page 64: Pattern Filter Operators

    LAN facilities, the Orbitor Ethernet bridge/router provides programmable filter masks that may be defined to act on any part of the Ethernet frame. In the examples below, several protocol types and combinations are presented to demonstrate the use of programmable filter masks to control the protocol traffic between Local Area Network segments.

  • Page 65: Protocol Type Field

    Programmable Filtering The Bridge Filter Patterns menu is located under the FILTER SET-UP MENU. Within the Bridge Filter Patterns Menu there exists a Help function that can be used as a reference during Bridge Filter Pattern creation. This Help function includes all of the logical operators that may be applied to the mask expression. Protocol Type Field Within an Ethernet frame, a protocol field exists at octet 12 and 13.

  • Page 66: Transport Control Protocol / Internet Protocol (Tcp/Ip

    Transport Control Protocol / Internet Protocol (TCP/IP) The previous example showed how to filter all Ethernet frames that contained an IP protocol packet. However, IP is used as the Network-layer protocol for more than 40 different Transport-layer protocols, TCP being only one of them.

  • Page 67: Dec

    Bandwidth Conservation Reducing traffic on each LAN segment is one benefit of the bridging functions of a Orbitor Ethernet bridge/router. There are several simple methods that may be used to provide a further reduction of inter-LAN traffic. The examples that follow present a few very simple methods to reduce inter-LAN traffic, without necessarily reducing resource capability.

  • Page 68: General Restrictions

    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 69: 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.

  • Page 70: 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 71: Appendix C - Frame Formats

    Appendix C — 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 72: Ethernet Type Codes

    Frame Formats ETHERNET TYPE CODES Type Code 0800 0801 0804 0805 0806 0807 6001 6002 6003 6004 6005 6006 6007 8035 803D 803F 809B 80D5 80F3 8137-8138 814C Octet Locations on an IP Routed TCP/IP Frame C-2 — Orbitor 3000 Reference Manual Description DOD IP X.75 Internet...

  • Page 73: Octet Locations On An Ipx Routed Novell Netware Frame

    Frame Formats Octet Locations on an IPX Routed Novell Netware Frame Octet Locations on a Bridged XNS Frame Orbitor 3000 Reference Manual— C-3...
  • Page 74 Address Connect, 2-3 ALARM Logs, A-6 ALARMS, A-1 AND ‘&’, B-9 Auto-Call, 2-2 Bandwidth Conservation, B-10 Bridge Pattern Filtering, B-7 Client IPX Watchdog Frames, 2-8 Console Pinouts, 3-2 CSU/DSU Back-to-Back Connection, 3-1 Crossover Cable, 3-2 Switches, 3-1 DEC, B-10 Event Logs, A-1 Filter all but IP, B-8 Filter all IP, B-8 Filter if Destination, B-1, B-2...

This manual is also suitable for:

Orbitor 3000

Table of Contents