Perle Systems IOLINK-520 manual

IOLINK-520 & IOLINK-PRO Reference Manual Issue 1 All Software Versions © Copyright 2001 by Perle Systems Ltd. 01/2001 Part # 197-41707[...]

IOLINK-PRO & 520 Reference Manual — 1.1 Section 1 — Introduction The IOLINK-PRO & 520 Routers The IOLINK-PRO & 520 routers provide 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 smal[...]

Introduction 1.2 — IOLINK-PRO & 520 Reference Manual 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. T he manufacturer of the device assigns M AC[...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.3 • Local router will r eceive the data frame and strip off the MAC portion. The resulting IP frame will be examined to determine the destination 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 wi[...]

Introduction 1.4 — IOLINK-PRO & 520 Reference Manual IP Header Details Every IP header has common fields of infor mation. The layout of the inf ormation is always th e same. Refer to the following diagram for a representation of the IP header. Figur e 1 - 2 IP Header Protocol The protocol section is used to indicate the protocol being used by[...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.5 Option s There are var ious options that may be s et for any IP f rame. Source Routing Source routing is used to predetermine t he path that the IP frame must tr avel through the network. Ther e are two types of sour ce routing: strict s ource routing and loose so urce routing. Strict source[...]

Introduction 1.6 — IOLINK-PRO & 520 Reference Manual Ping The “ping” message is a ctually a query sta tus message that may be sent to devices on the LAN to determine their operation status. The LAN device will reply with a mes sage if it is active. Time and Ma sk server Two other ICMP me ssages a re used to query the time and/or subne t m[...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.7 RIP—Routing Information P rotocol 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 p[...]

Introduction 1.8 — IOLINK-PRO & 520 Reference Manual IPX Routing and The IOLINK-PRO & 520 Routers The IOLI NK 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, [...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.9 Node Addresses The Node Number identifies th e individual stations in a Network. I n IPX devices, this addr ess is ass igned automatically and is identical to the MAC address. This means that the Node Number is s elf-configuring, and will be unique within the Network because the MAC address [...]

Introduction 1.10 — IOLINK-PRO & 520 Reference Manual 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. Servers send SAP broadcasts regularly to [...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.11 SAP Requests Sometimes Clients will need to find out if a specific Server is available. This may occur immediately after a Client is brought up, and before it has received any SAP broadcasts. T he Client (or a new Server) sends out a SAP Request broadcast asking for a specific Server. That [...]

Introduction 1.12 — IOLINK-PRO & 520 Reference Manual RIP/X Requests A Client may also request a route to a given network or server. To do so, the Client generates a Route Request broadcast that the routers hear, and routers that know of the route requested will respond to the originating station. In this way a new Client may find routes with[...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.13 The Initial Bridging Process Each time a IOLINK router is powered up, it will perform extensive hardware and s oftware tests to ensure the integrity of the unit and its attached LAN and Link interfaces. Upon success ful completion of the power-up diagnostics, the IOLINK router will follow r[...]

Introduction 1.14 — IOLINK-PRO & 520 Reference Manual Forwarding Unknown Dest ination Addresses When a frame is received f rom a LAN segment with an unknown dest ination address (an addres s that does not yet exist in the filter table), the bridge will forward the frame to the other segment, logging the address, and marking the location as ?[...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.15 Aging Except ion “Permanent” address entries are an exception to the aging rule. A permanent address is one that is not subject to the aging timer and will remain in the filter table for an indefinite period of time. A table is reserved for permanent address entries, separate from the t[...]

Introduction 1.16 — IOLINK-PRO & 520 Reference Manual IOLINK R outer Feat ure Definit ions Telne t A Telnet LAN station or another IOLINK router has the ability to connect to the Operator Interface of any IOLINK router supporting the Telnet feature. W ith the Telnet feature, all IOLINK routers on a network may be managed from a single point. [...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.17 0 1 2 3 4 5 6 7 Graphic Database Post Script ASCII C Source Spreadsheet Binary Pre-compressed File Type Compress ion Ratio Figure 1 - 5 Typic al Compression Ra tios by File Type Data compression will give a 56/64 Kbps link an effective throughput range from 112/128 Kbps when transferring bi[...]

Introduction 1.18 — IOLINK-PRO & 520 Reference Manual WAN Topol ogie s The IOLINK router may be connected to other IOLINK routers in two configurations: Multipoint or Point-to-Point. The WAN routing method used is set in the WAN Set-Up Menu under the Link Operation option. Point-to -Point In a Point-to-Point configuration, two IOLINK routers [...]

Introduction IOLINK-PRO & 520 Reference Manua — 1.19 To set up a Bandwidth on Demand installation, you would first connect the second link of the IOLINK router to a public circuit-switched network using the appropriate interface device. You would use high-speed modems with telephone lines, terminal adapters with an ISDN network, or digital mo[...]

Introduction 1.20 — IOLINK-PRO & 520 Reference Manual Multipoint A simple Multipoint configuration would consist of a head office and two remote offices. C ost comparisons might reveal that it is less expensive to use a dial-up line during business hours only instead of a permanent leased line. One IOLINK router will be installed at each offi[...]

IOLINK-PRO & 520 Reference Manual — 2.1 Section 2 — ISDN Connection Management IOLINK PRO & 520 ISDN Connection Management In the world of ISDN the ability to decrease connection time is a financial bonus in the LAN interconnecting marketplace. If ISDN connections can be controlled so that a minimum amount of cost is incurred while full[...]

ISDN Connection M anagement 2.2 — IOLINK-PRO & 520 Reference Manual Auto-Call (Time- of-Day Connections) An Auto-Call connection is an ISDN connect ion that is established each time t he IOLINK router attempts to start th e link. This starting of the links occurs each time an I OLINK router power s up or when the link goes through a restart o[...]

ISDN Connection M anagement IOLINK-PRO & 520 Reference Manual — 2. 3 Address Co nnect An Address Connect connection is an ISDN connection that is established to a specific destination IOLINK router dependent upon the destination network address contained within traffic received from the local LAN. When a device on the local LAN wishes to esta[...]

ISDN Connection M anagement 2.4 — IOLINK-PRO & 520 Reference Manual 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 Connection M anagement IOLINK-PRO & 520 Reference Manual — 2. 5 Protocol Awaren ess For Connection Management to be effective, each of the IOLINK routers must be aware of the protocols used within the data being trans ferred over the I SDN calls between them. IP and IPX Client -Server sess ions are established between devices located on [...]

ISDN Connection M anagement 2.6 — IOLINK-PRO & 520 Reference Manual When the IOLI NK router receives a keepalive packet from the LAN for one of the sessions , the IOLINK router will not activate the ISDN call and will not pass the keepalive packet to the remote LAN. Th e IOLINK router will generate a response to the keepalive packet and send [...]

ISDN Connection M anagement IOLINK-PRO & 520 Reference Manual — 2. 7 IP Specif ics IP Address Connect As stated pr eviously, an IP Address Connect connection is an ISDN connection that is established to a specif ic destination IOLINK router dependent upon the des tination IP address contained within IP traffic received from the local LAN. Thi[...]

ISDN Connection M anagement 2.8 — IOLINK-PRO & 520 Reference Manual IPX Specif ics RIP/IPX and SAP/IPX IOLINK I SDN routers incorpor ate a 3 second settling time fo r IPX RIP and SAP updates. This means t hat an IOLINK will wait for three seconds after an initial change in the network is reported before transmitting that change on to the rema[...]

IOLINK-PRO & 520 Reference Manual — 3.1 Section 3 — Link Interfaces Reference Pinout Informat ion 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. When connecting two bridge/routers back-to-back without modems[...]

Link Interfaces Reference 3.2 — IOLINK-PRO & 520 Reference Manual The IOLINK-PRO and 520 routers are currently produced with LXT CSU/DSU interface modules which have the ir link spee d configured in software (ple ase see the PPP menus ma nual for configuration options); however, the earlier model ATL CSU/DSU module is still compatible with th[...]

Link Interfaces Reference IOLINK-PRO & 520 Reference Manual — 3.3 Conso le Pinout s The connector shown here and pinouts described here correspond to the connector labeled “Console” on the back of the IOLINK-PR O & 520. 13 1 25 14 DB25 Female DCE Contact Number CCITT Circui t Number Circui t Circui t Name Direction To From DCE DCE 1 1[...]

Link Interfaces Reference 3.4 — IOLINK-PRO & 520 Reference Manual CSU/DS U Module: The CSU/D SU interface m odule uses a standard RJ45 s ervice connector, pinout specification RJ48S. Figure 3 - 5 Rear View of the CSU-DSU Connector The LXT411 CSU/D SU li nk connection is set to operate at 64 Kbps by defaul t. The link may be set to 56 Kbps via[...]

Link Interfaces Reference IOLINK-PRO & 520 Reference Manual — 3.5 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 IOLINK-PR O & 520. 13 1 25 14 DB25 Female DTE Contact Number CCITT Circui t Number Circui t Circui t Name Direction To[...]

Link Interfaces Reference 3.6 — IOLINK-PRO & 520 Reference Manual V.11 & X .21 Link Pinout s The connector shown here and pinouts described here correspond to the connector labeled “V.11/X.21” on the back of the IOLINK-PRO & 520. 1 8 9 15 DB15 Female DTE Contact Number X.21 Circui ts Reference Circui t Name Direction To From DCE D[...]

Link Interfaces Reference IOLINK-PRO & 520 Reference Manual — 3.7 RS442 & RS530 Link Pinouts The connector shown here and pinouts described here correspond to the connector labeled “RS530” on the back of the IOLINK-PR O & 520. 13 1 25 14 DB25 Female DTE Contact Number Circui t Circui t Name Direction To From DCE DCE 1 Shield Prote[...]

Link Interfaces Reference 3.8 — IOLINK-PRO & 520 Reference Manual V.35 Link Pinouts 13 1 25 14 DB25 Female DTE DB25 Contact Number M.34 Contact Number CCITT Circui t Number Circui t Name Direction To From DCE DCE 1 A Protective Gr ound NA 2 ---------- 3 ---------- 4 C 105 Request t o Send X 5 ---------- 6 E 107 Data Set Ready X 7 B 102 Signal[...]

Link Interfaces Reference IOLINK-PRO & 520 Reference Manual — 3.9 RS232 Null-Modem Ca ble Configura tion Figure 3 - 11 RS232 Null-Modem Cable The connecting cable must be a shielded cable. This cable is needed w hen it is necessary to connect two units back-to- back and a set of modems is not available. Not e that this cable specif ies DB25 c[...]

Link Interfaces Reference 3.10 — IOLINK-PRO & 520 Reference Manual V.35 Null-Mo dem Cable Configura tion Prot ective GND T ransmitted Data (A) T ransmitted Data (B) Received Dat a (A) Received Dat a (B) T ransmitter S ignal Eleme nt Timi ng (A) T ransmitter S ignal Eleme nt Timi ng (B) Receiver Si gnal Eleme nt Timin g (A) Receiver Si gnal El[...]

Link Interfaces Reference IOLINK-PRO & 520 Reference Manual — 3.11 RS530 Null-Modem Ca ble Configura tion Shiel d T ransmitted Data (A) T ransmitted Data (B) Received Data (A) Received Data (B) Request T o Send ( A) Request T o Send ( B) Clear T o Send (A) Clear T o Send (B) DCE Ready (A) DCE Ready (B) DTE Ready (A) DTE Ready (B) Signal Groun[...]

Link Interfaces Reference 3.12 — IOLINK-PRO & 520 Reference Manual RS530 To RS449 Conversion Cable T ransmitted Data (A) Data T erminal Ready (A) T ransmitted Data (B) Data T erminal Ready (B) Received Data (A) Receiver Si gnal Eleme nt Timing (DCE S ource) (A) Received Data (B) Receiver Si gnal Eleme nt Timing (DCE S ource) (B) Received Li n[...]

Link Interfaces Reference IOLINK-PRO & 520 Reference Manual — 3.13 V.11/X .21 Null-Modem Ca ble Config uratio n Figure 3 – 15 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. This cable is n[...]

Link Interfaces Reference 3.14 — IOLINK-PRO & 520 Reference Manual WAN Link Cont rol-S ignal Oper ation CTS flow control is not supported. It is assumed that Dial In/Dial Out modes of dial-up operation will be configured externally to the bridge/router, i.e. on the attached modem, by setting Originate Only/Answer Only modes. A dataset or DSU/[...]

IOLINK-PRO & 520 Reference Manual — A.1 Appendix A - Event Logs The IOLINK router generates event logs for various functions performed by the bridge/router. All of the event logs are stored in the int ernal event log file, which is accessible t hrough the Network Events menu. Certain event logs ar e classified as alar ms because they are deem[...]

Event Logs A.2 — IOLINK-PRO & 520 Reference Manual Completed BACP negotiation with <remote site alias> Generated when the Bandwidth Allocation Control Protocol negotiation has been completed with the remote site device associated wit h the stated remote s ite profile. Once BACP negotiat ions are complete, the two rout ers will negotiate[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.3 DHCP services – release. <IP addres s> released. Generated when IP address displayed is released from its assignment to a device and put back in the IP pool for re- assignme nt. Error executing: XXXXXX Generated when an error is detected loading back a configuration. The invalid comma[...]

Event Logs A.4 — IOLINK-PRO & 520 Reference Manual LCP X establishing Generated when the Link Control Protocol of a PPP link or remote site is establishing between this device and the remote site PPP device. LCP X no reply to Y Echo-Requests Generated just prior to a link going down. The link or remote site has gone down due to no replies to [...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.5 Link X CSU/DSU: Loopback Started Generated when the CSU/DSU link module starts a new loopback test. Link X - CSU/DSU out of service Generated when the CSU/DSU is in communication with t he local telco, but is not connected to the remote partner CSU/DSU. Link X CSU/DSU: No Signal Generated whe[...]

Event Logs A.6 — IOLINK-PRO & 520 Reference Manual LMI discarding STATUS on link X – Enquiries not started Generated when the bridge/rout er discards a Status message received from the f rame 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 w h[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.7 Starting BACP negotiation with <remote site alias> Generated when the Bandwidth Allocation C ontrol Protocol negotiation has been initiated with the remote site device asso ciated with the stated r emote site profile. Starting BCP negotiation with <remote site alias> Generated whe[...]

Event Logs A.8 — IOLINK-PRO & 520 Reference Manual TFTP: <IP address> getting filena me A LAN device with IP address displayed is getting a file (filename) from the bridge/router. TFTP: <IP address> putting filename A LAN device with IP address displayed is putting a file (filename) onto the bridge/router.[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.9 Alarm Logs: * Auto-learning of LMI type on link X unsuccessful Generated when the LMI type on a link is not successf ully auto-learned. * Backu p Battery is bad The backup battery power for memory backup has dropped below operating level, replace the batteries (see Installation and Applicatio[...]

Event Logs A.10 — IOLINK-PRO & 520 Reference Manual * Closing remote site X (no NCPs open) Generated when no Network Control Protocols operating. * Closing remote site X (nonexistant) Generated w hen remote site being dele ted by the operator. * Closing remote site X (not enabled) Generated w hen remote site autoca ll being disabled by the op[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.11 * Download aborted – Incomplete file Generated when a TFTP download is abortet before the file transfer is complete * Download aborted – Invalid FCS Generated when there is a checks um failure after a file download. * Download aborted – Incompatible boot code Generated when the operati[...]

Event Logs A.12 — IOLINK-PRO & 520 Reference Manual * FTP server added to firewall The IP addr ess of the FT P server added to t he table of services available thr ough the firewall. * FTP server remove d from firewall The IP addr ess of the FT P server removed fr om the table of services available t hrough the firewall. * Gopher server added[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.13 * Link X Connected Generated when and end-to-end ISDN call has been established. * Link X connection rejected Generated when Link X connection is being terminated as it could not be attached to a remote site. This may be due to usage limits or suspe nsion resumptions. * Link X - CSU/DSU not [...]

Event Logs A.14 — IOLINK-PRO & 520 Reference Manual Code Description 033 034 035 036 037 038 039 Circ uit out of ord er No circuit/channel available Destination unattainable Out of or der Degraded servic e Network ou t of order Transit de lay range c annot be achie ved 040 041 042 Throughput r ange cannot be achieve d Temporary failure Switch[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.15 * Link X, DLCI Y atta ched to remote site <re mote site alias> Generated for frame relay applications when a connection has been made for the DLCI associated with t he remote site ali as. * Link X down Generated when a WAN link goes down. * Link X down to <remote s ite alias> Gen[...]

Event Logs A.16 — IOLINK-PRO & 520 Reference Manual * Link X up at Y baud Generated when frame relay link is es tablished. * Link X up to <remote s ite alias> Generated when a WAN link connection to the sp ecified remote site comes up. * Local DNS server added to firewall The IP addr ess of the Lo cal DNS server added to the table of se[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.17 * No ISDN line available for r emote site <remote site alias> All ISDN lines are currently in use; none are available for the new connection requested. May be generated when CMCP is enabled and more I SDN calls are attempted than t here are available ISDN lines. * No ISDN resour ce ava[...]

Event Logs A.18 — IOLINK-PRO & 520 Reference Manual * Remote site <remot e site alias> frame relay clos ing Generated when frame relay is diabled on t he link to the specified remot e site. * Remote site <remote site a lias> resu med Generated when the connection to the s pecified remote site has been res umed. * Remote Site <r[...]

Event Logs IOLINK-PRO & 520 Reference Manual — A.19 * TFTP: Abor t. Error (#) received Aborted a TFTP s ession because of the reception of a TFTP error mes sage from the connected device. The errors ar e: 0 - not defined, 1 - file not found, 2 - access violation, 3 - disk f ull or allocation exceeded, 4 - illegal TFTP operation, 5 - unknown t[...]

Event Logs A.20 — IOLINK-PRO & 520 Reference Manual PPP Security Logs: CHAP authentic ation 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 <r emote site alias> Generated w hen the remote site route r failed a CHAP authentic at[...]

IOLINK-PRO & 520 Reference Manual — B.1 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 discri[...]

Programmable Filtering B.2 — IOLINK-PRO & 520 Reference Manual Security—“Filt er if Destination” Filter if Destination is a function that allows you to filter an Ethernet frame bas ed on the des tination of its address. If the destination address equals the address that the Filter if Destination function has been applied t o, the frame [...]

Programmable Filtering IOLINK-PRO & 520 Reference Manual — B.3 Security—“Filt er if Source” Filter if Sour ce is a function that allows you to filter an Ether net frame if the s ource address of the frame equals the address th at the Filter if Source f unction has been applied to. Example: Assume that a Personal Computer is located on s[...]

Programmable Filtering B.4 — IOLINK-PRO & 520 Reference Manual 8 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 [en[...]

Programmable Filtering IOLINK-PRO & 520 Reference Manual — B.5 4 From the MAC ADDRESS FILTERS MENU, make s ure 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. 5 From the MAC ADDRE SS FILTERS MENU, enter a 1. This [...]

Programmable Filtering B.6 — IOLINK-PRO & 520 Reference Manual 2 From the CONFIGURATION MENU, enter an 8. This will place you at the FILTER SET-UP MENU, where access to the individual filt ering menus is obtained. 3 From the FILTER SET-UP MENU, e nter a 1. This will place you at the MAC ADDRESS FILTERS MENU, where access to the MAC Address fi[...]

Programmable Filtering IOLINK-PRO & 520 Reference Manual — B.7 Pattern Fi lter Operators The following operators are used in creating Pattern filters and will be dis cussed further in the following pages . For additio nal information refer to the octet locations diagrams at the back of this manual. Each octet location may contain a HEX value.[...]

Programmable Filtering B.8 — IOLINK-PRO & 520 Reference Manual The Bridge Filter Patterns menu is located under the FILTER SET-UP MENU. Within the Br idge 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 operato rs that may b[...]

Programmable Filtering IOLINK-PRO & 520 Reference Manual — B.9 Transport Con trol Protocol / Int ernet Protoc ol (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[...]

Programmable Filtering B.10 — IOLINK-PRO & 520 Reference Manual DEC DEC uses protocol types 6000 to 600F, and although s ome 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 las t four bits (a nibble) of the ty[...]

Programmable Filtering IOLINK-PRO & 520 Reference Manual — B.11 General Restrictions Bridge Filter Masks may be created to generally restrict acces s for various purposes. Some of thes e purposes may be to filter specific combinations of information. This section will generally depict masks that may be created to control traffic across t he b[...]

Programmable Filtering B.12 — IOLINK-PRO & 520 Reference Manual Mask Combi nations Mask combinations may be required to ens ure that a frame is sufficiently qualified bef ore the decision to filt er is made. The qualification a frame must go through before a filter decision is made depends on the reason for the filter. Nonetheless, a f ew exa[...]

Programmable Filtering IOLINK-PRO & 520 Reference Manual — B.13 IP Router Pattern F ilterin g Pattern filtering may be used on any portion of the IP frame. IP pattern filtering behaves the same as bridge pattern filterin g, except the start of the IP frame is offset 0, because th e IP router f unction of the bridge/router handles only the IP [...]

[...]

IOLINK-PRO & 520 Reference Manual — C.1 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 fr ame represen[...]

Frame Formats C.2 — IOLINK-PRO & 520 Reference Manual ETHERNET TYPE CODES Ty pe Code Description 0800 DOD IP 0801 X.75 Internet 0804 Chaosnet 0805 X.25 Level 3 0806 A RP 0807 XNS Compatibility 6001 DEC MOP Dump/Load 6002 DEC MOP Remote Consol e 6003 DEC DECNET Phase IV Route 6004 DEC LA T 6005 DEC Diagnostic Prot ocol 6006 DEC Customer Protoc[...]

Frame Formats IOLINK-PRO & 520 Reference Manual — C.3 Octet Locations on an IPX Routed N ovell Netware Fram e Octet Locations on a Bridged XNS Frame[...]