1. Manuals
  2. Brands
  3. Perle Manuals
  4. Wireless Router
  5. P2600
  6. Reference manual

Perle P2600 Reference Manual

Bridge/router
Hide thumbs Also See for P2600:
Table of Contents

Advertisement

Quick Links

Download this manual
Perle P2600
Bridge/Router

Reference Manual

All Software Versions
Part number 5500079-12
© Copyright 2002 by Perle Systems Ltd.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the P2600 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Perle P2600

Summary of Contents for Perle P2600

  • Page 1: Reference Manual

    Perle P2600 Bridge/Router Reference Manual All Software Versions Part number 5500079-12 © Copyright 2002 by Perle Systems Ltd.

  • Page 2: Section 1 - Introduction

    The P2600 router can be thought of as a group of discrete functions combined in a single box. The first functional module is the 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.

  • Page 3: Arp-Address Resolution Protocol

    Local router will see ARP request and send an ARP reply to the originating station with the MAC address of the local router port. • Originating station will send the data frame addressed to the IP address of the destination station, and the MAC address of the local router port. P2600 Reference Manual — 3...
  • Page 4 Introduction • Local router will receive 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 will see that the destination router is the next router.
  • Page 5 Each of the fragments is assigned a fragment offset value, which determines where the fragment fits into the original IP frame. The P2600 router will accept fragmented frames directed to itself and reassemble them, but it will not fragment frames.
  • Page 6 Introduction 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. There are several different messages, as discussed below. Unreachable The “unreachable” message is sent back to the originating station when the path to the destination network has disappeared.

  • Page 7: Update Mechanism

    If a router has not heard from an adjacent router in 180 seconds, the local router will mark the adjacent router as unreachable and start to adjust the routing table, if necessary. P2600 Reference Manual — 7...

  • Page 8: Ipx Addressing

    Introduction IPX Routing and The P2600 Router The P2600 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 Transport Control field if Novell decides to use the excess capacity. 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. P2600 Reference Manual — 9...
  • Page 10 Introduction 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 identify themselves, including their address and what type of service they offer (File Server, Print Server, Fax Server, etc.).

  • Page 11: Server Types

    RIP/X broadcast, followed 15 seconds later by a SAP broadcast, followed 15 seconds later by another RIP/X broadcast, etc., etc. The SAP and RIP/X broadcasts are sent every 30 seconds as required, but they are staggered by 15 seconds to spread the overhead. P2600 Reference Manual — 11...
  • Page 12 The P2600 Router will also fit right into those environments that may require more than one bridge by using the IEEE 802.1D Spanning Tree Protocol. With this protocol, the P2600 Router will perform automatic network reconfiguration in the event of a link failure to one of the LAN segments.
  • Page 13 The Initial Bridging Process Each time a P2600 router is powered up, it will perform extensive hardware and software tests to ensure the integrity of the unit and its attached LAN and Link interfaces. Upon successful completion of the power-up diagnostics, the P2600 router will follow rules to “learn”...
  • Page 14 In summary, the P2600 router will “learn” the location of a station by examining the source Ethernet address, and will “filter” frames based on destination address. A frame received from one segment that is of “unknown”...
  • Page 15 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 P2600 router. Filled Address Table Sometimes filter address table may become full.
  • Page 16 The IP address of another bridge/router may be assigned a name to simplify the connection process. Telnet connection to the other P2600 router may be established by entering either the name or the IP address of that router. Refer to the Remote Site Set-Up Menu (under Configuration / WAN Set-UP) for more information on adding names to the bridge/router.
  • Page 17 LANs to achieve a given performance level, and also allows the use of lower-cost transmission facilities. Uncompressed Compressed Throughput in Kbps Binary Mixture Graphic File Type Figure 1 - 6 Typical Throughput Over 56 Kbps Link P2600 Reference Manual — 17...

  • Page 18: Point-To-Point

    The Time of Day connect feature may be used in a Multipoint configuration to provide specific hours of access. Bandwidth On Demand Each P2600 router has the ability to automatically enable or disable a second link based on traffic activity, time of day, or main link failure.
  • Page 19 With the time schedule set to have the link active from 8 am to 6 pm each day of the week, the P2600 router will establish the link and keep it active during those hours only.
  • Page 20 One P2600 router will be installed at each office (for a total of three units). Each P2600 router at the remote office locations will connect to a separate link on the P2600 router at the head office.

  • Page 21: Section 2 - Isdn Connection Management

    The generation of the regular status inquiries and responses normally generated by the two devices involved in the LAN connection is performed by the P2600 ISDN bridge/router while the ISDN call is suspended. Wide Area Network Topologies Supported Two types of Wide Area Network (WAN) topologies are supported with Connection Management 1.
  • Page 22 ISDN Connection Management Auto-Call (Time-of-Day Connections) An Auto-Call connection is an ISDN connection that is established each time the router attempts to start the link. This starting of the links occurs at the times specified by the Time-of-Day Activation Schedule, or each time an router powers up or when the link goes through a restart.

  • Page 23: Manual Call

    ISDN Connection Management Address Connect An Address Connect connection is an ISDN connection that is established to a specific destination router 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 24: Connection Process

    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 some remote sites and a dynamic connection is required to other sites. A dynamic connection indicates that the remote site for the ISDN call will change depending upon what destination IP address is required for the connection..
  • Page 25 IP and IPX Client-Server sessions are established between devices located on the LANs that are routed by the P2600 router. If the router is to manage the ISDN calls between the routed LANs, the routers 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 26: Idle Timer

    P2600 routers incorporate a settling time for routing updates. This means that an router will wait after an initial change in the network is reported before transmitting that change on to the remaining routers connected on the Wide Area Network.

  • Page 27: Termination Process

    RIP—Routing Information Protocol The P2600 ISDN routers incorporate a 3 second settling time for IP RIP updates. This means that an router will wait for three seconds after an initial change in the network is reported before transmitting that change on...
  • Page 28 ISDN Connection Management IPX Specifics RIP/IPX and SAP/IPX ISDN routers incorporate a 3 second settling time for IPX RIP and SAP updates. This means that an router will wait for three seconds after an initial change in the network is reported before transmitting that change on to the remaining routers connected on the Wide Area Network.

  • Page 29: Section 3 - Link Interfaces Reference

    Section 3 — Link Interfaces Reference Pinout Information 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, a null-modem cable is required to crossover the pins on the links.
  • Page 30 1 is down (on), the normal position, the module receive clocks from the connected network. When switch 1 is up (up), the module will generate clocks. When a pair of P2600 routers are connected back-to-back with CSU/DSU link modules one module must be set to generate clocks and one module must be set to receive clocks.

  • Page 31: Console Pinouts

    The connecting cable must be a shielded cable. When connecting the P2600 console directly to a modem, a null modem cable must be used because both the P2600 console and the modem are DCE devices. A null modem cable with pinouts according to the following figure must be used.
  • Page 32 Link Interfaces Reference CSU/DSU Module: The CSU/DSU interface module uses a standard RJ45 service connector, pinout specification RJ48S. C S U /D S U Figure 3 - 4 Rear View of the CSU-DSU Connector 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.
  • Page 33 Link Interfaces Reference 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 P2600. DB25 Female DTE CCITT Direction Contact Circuit Circuit From Number Number...
  • Page 34 Link Interfaces Reference V.11 & X.21 Link Pinouts The connector shown here and pinouts described here correspond to the connector labeled “V.11/X.21” on the back of the P2600. DB15 Female DTE X.21 Direction Contact Circuits Circuit From Number Reference Name...
  • Page 35 Link Interfaces Reference RS442 & RS530 Link Pinouts The connector shown here and pinouts described here correspond to the connector labeled “RS530” on the back of the P2600. DB25 Female DTE Direction Contact Circuit From Number Circuit Name DCE DCE...
  • Page 36 Link Interfaces Reference V.35 Link Pinouts The connector pinouts described here correspond to the DB25 connector on the back of the P2600. DB25 Female DTE DB25 M.34 CCITT Direction Contact Contact Circuit Circuit From Number Number Number Name DCE DCE...
  • Page 37 Link Interfaces Reference RS232 Null-Modem Cable Configuration D B 2 5 M A LE D B 2 5 M A LE S h ie ld S h ie ld R e ce iv ed D a ta Tran s m itted D ata R e ce iv ed D a ta Tran s m itted D ata D a ta S et R e ad y...

  • Page 38: Null-Modem Cable Configuration

    Link Interfaces Reference V.35 Null-Modem Cable Configuration DB25 MALE DB25 MALE Protective GND Protective GND Received Data (A) Transmitted Data (A) Received Data (B) Transmitted Data (B) Received Data (A) Transmitted Data (A) Received Data (B) Transmitted Data (B) Receiver Signal Element Timing (A) Transmitter Signal Element Timing (A) Transmitter Signal Element Timing (B) Receiver Signal Element Timing (B)
  • Page 39 Link Interfaces Reference RS530 Null-Modem Cable Configuration DB25 MALE DB25 MALE Shield Shield Received Data (A) Transmitted Data (A) Transmitted Data (B) Received Data (B) Received Data (A) Transmitted Data (A) Transmitted Data (B) Received Data (B) DCE Ready (A) Request To Send (A) DCE Ready (B) Request To Send (B)
  • Page 40 Link Interfaces Reference RS530 To RS449 Conversion Cable DB25 MALE DB37 MALE/FEMALE Transmitted Data (A) Transmitted Data (B) Received Data (A) Received Data (B) Received Line Signal Detector (A) Received Line Signal Detector (B) Data Set Ready (A) Data Set Ready (B) Request to Send (A) Request to Send (B) Clear to Send (A)
  • Page 41 Link Interfaces Reference V.11/X.21 Null-Modem Cable Configuration Figure 3 – 14 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 needed when it is necessary to connect two units back-to-back and a set of modems is not available.
  • Page 42 Link Interfaces Reference WAN Link Control-Signal Operation 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/CSU can be used for a leased-line operation.

  • Page 43: Appendix A - Event Logs

    Appendix A - Event Logs The P2600 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...
  • Page 44 Event Logs Completed BACP negotiation with <remote site alias> Generated when the Bandwidth Allocation Control Protocol negotiation has been completed with the remote site device associated with the stated remote site profile. Once BACP negotiations are complete, the two routers will negotiate when required to bring up the second link.
  • Page 45 Event Logs Generated when a client declines an address offered by the DHCP service, usually because the client has found from some other source that the address is unavailable. DHCP services – release. <IP address> released. Generated when IP address displayed is released from its assignment to a device and put back in the IP pool for re- assignment.
  • Page 46 Event Logs...
  • Page 47 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 P2600. Link X CSU/DSU: Line ERROR Generated when the CSU/DSU link module is in an unknown error state.
  • Page 48 Generated when the CSU/DSU link module cannot establish communications with the local telco. Link X CSU/DSU: Reset Generated when the P2600 has initiated a reset of the CSU/DSU link module. Link X - external loopback results[Total: X] [Good: X] [Errors: X] Generated after the CSU/DSU link module has completed an external loopback.
  • Page 49 Event Logs Refused connection attempt from <remote site alias> Generated when a connection attempt to a remote site is refused by that site Remote Site <remote site alias> re-establishing due to multilink mismatch Generated when multilink negotiated on by one end of the link and off by the other. The value for multilink will be toggled on this device and LCP will be re-negotiated.
  • Page 50 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 51: 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. * Backup Battery is bad The backup battery power for memory backup has dropped below operating level, replace the batteries (see Installation and Applications Manual, Appendix D.
  • Page 52 Event Logs * Closing remote site X (IPX demand RIP) Generated due to the failure of IPX demand RIP. * Closing remote site X (last session) Generated due to the termination of the last session. * Closing remote site X (link disabled) Generated due to the link being disabled by the operator.
  • Page 53 Event Logs * DHCP server – out of addresses in IP pool Generated when the last address from the DHCP IP Address pool has been assigned to a device. * Download aborted – Incomplete file Generated when a TFTP download is aborted before the file transfer is complete * Download aborted –...
  • Page 54 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 55 Event Logs * Link X Disconnect: Y Generated when the disconnect of an ISDN call is completed. This event is generated on both sides of the ISDN call. The cause will be one of the causes as specified in the CCITT Recommendation Q.931. Causes of “normal call clearing”, “User busy”, and “Number changed”...
  • Page 56 Event Logs Code Description Incoming calls barred within CUG Call waiting not subscribed Bearer capability not authorized Bearer capability not presently available Service or option not available, unspecified Bearer capability not implemented Channel type not implemented Transit network selection not implemented Message not implemented Requested facility not implemented Only restricted digital information bearer capability is available...
  • Page 57 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 58 Event Logs * Link X up at Y baud Generated when frame relay link is established. * Link X up to <remote site alias> Generated when a WAN link connection to the specified remote site comes up. * Local DNS server added to firewall The IP address of the Local DNS server added to the table of services available through the firewall.
  • Page 59 Event Logs * No available remote site for leased line X Generated when attempting to set up a default leased line remote site and the remote site table is filled, no space is available to create another entry. The user must manually edit the table to remove some remote site profiles before another entry can be made.
  • Page 60 Event Logs * Remote Site <remote site alias> already connected Generated when a connection is attempted to a site that is already connected to this router. * Remote site <remote site alias> connected Generated when the specified remote site has been connected for connection management. * Remote site <remote site alias>...
  • Page 61 Event Logs * Telnet server added to firewall The IP address of the Telnet server added to the table of services available through the firewall. * TFTP: Abort. ACK retry exceeded Aborted a TFTP session because the bridge/router did not receive a new data packet within the TFTP “T1” times “N2”...
  • Page 62 Event Logs * WWW (HTTP) server added to firewall The IP address of the Telnet WWW (HTTP) added to the table of services available through the firewall. * X count overflow. Reset to history size Generated when the number of items logged exceeds the space available. X = “ALARM” or “EVENT”...
  • Page 63 CHAP failed to complete Generated when the remote site router sent a CHAP challenge and this P2600 sent a response, but no further information was received from the remote site router. CHAP login refused by <remote site alias>...

  • Page 64: Appendix B - Programmable Filtering

    The P2600 router provides three built-in functions – in addition to defined programmable masks – to control the access to resources. The first function is “Filter if Source”; the second is “Filter if Destination.” The third function allows you to change the filter operation from “positive”...
  • Page 65 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 66 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 67 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 68 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 69 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 70 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.

  • Page 71: Internet Protocol (Ip)

    Ethernet frame, and therefore is transparent to the normal bridging function. If you would like to discriminate against a particular protocol to prevent its use of the bridged LAN facilities, the P2600 router provides programmable filter masks that may be defined to act on any part of the Ethernet frame.
  • Page 72 Programmable Filtering The parenthesis simply ensures that the NOT operator will apply to the entire expression. In this case, whenever a frame is received, the frame will be filtered if the protocol type is NOT equal to 0800 (IP). Only one filter pattern may be used that contains the NOT operator.
  • Page 73 Programmable Filtering 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 74 Bandwidth Conservation Reducing traffic on each LAN segment is one benefit of the bridging functions of a P2600 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 75: 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 76 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 77 IP frame, and therefore is subject to the IP routing function. If you would like to discriminate against a particular protocol to prevent its usage of the routed LAN facilities the P2600 Router provides programmable filter masks that may be defined to act on any part of the IP frame.
  • Page 78 Apendix 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 79: Frame Formats

    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 80 Frame Formats Octet Locations on an IPX Routed Novell Netware Frame Octet Locations on a Bridged XNS Frame...

Table of Contents