Digi 16, TS8 manual About RIP Routing Updates

Page 45

About RIP Routing Updates

Introduction

RIP defines a method for propagating routing information among routers. It provides IP software with the information needed to make intelligent routing decisions.

The information, passed in RIP updates packets from router-to-router, consists of two items, a network ID and a hop count. A hop count is the number of routers through which a packet must pass on its way from a source to a destination network.

RIP Example

In the example that follows, Router R1 “advertises” (using RIP) that it can reach Net 1 in one hop. When Router R2 receives this advertisement, it then knows that since it is on a common network with R1 that it can reach Net 1 in two hops. It advertises this fact to other routers in the network, who use this information to calculate their own routes to Net 1.

Net 1

R1

Net 2

R2

Net 3

Net 4

R3

Problem with RIP: Sending Updates Across a WAN

RIP can be an expensive way to handle routing if RIP updates are regularly sent across lines that charge by traffic volume or usage time. Neither of these, of course, applies to LANs or leased lines. Because of these cost considerations, PortServer TS 8/16 lets you turn RIP off on some or all serial links.

Problem with RIP: Slow Convergence

Slow convergence is a problem that can arise from the method RIP uses to disseminate routing information. In the preceding figure,

1.R1 advertises that it can reach Net 1 in one hop.

2.R2 then advertises that it can reach Net 1 in two hops

3.R3 then advertises that it can reach Net 1 in three hops.

What happens if R1’s link to Net 1 goes down? First it realizes that its one-hop route to Net 1 is no longer available. But it hears that R2 can reach Net 1 in two hops, so it updates its routing table to say it can reach Net 1 in three hops, the one hop to R2 and the two hops R2 says it needs to reach Net 1.

R1 then advertises that it can reach Net 1 in three hops. R2 hears the advertisement and realizes that if R1 needs three hops to get to Net 1 then it needs to update its own routing tables to reflect that fact, because it knows that its route to Net 1 is always one more hop than R1 requires. Consequently, it updates its routing tables to say that it can reach Net 1 in four hops. This can go on until the hop count to Net 1 reaches 16, which RIP defines as an unreachable destination.

Combatting RIP’s Slow Convergence Problem

There are two methods to combat RIP’s slow convergence problem, both of which PortServer TS 8/16 implements.

The first is called “split horizon,” which stipulates that learned routes are not propagated from the interface on which they are learned. Had split horizon been used in the preceding example, R2 would not have advertised to R1 that it could reach Net 1. Consequently, R1 would never have

Configuring IP Routing

9-3

Image 45
Contents PortServer TS 8/16 Configuration and Administration Guide Page Contents Chapter Configuring Users Page This Chapter IntroductionSetup Overview About Entering Commands on the Command Line About This GuideSupported Devices Other Documents in the Library Access Resource CD CardConfiguring the PortServer TS 8/16 from a Telnet Session About Configuration MethodsConfiguring the PortServer TS 8/16 from the Web Interface Downloading a Configuration FileLogging On As Root from the Command Line Configuration PrerequisitesAccessing the Command Line from a Telnet Session Accessing the Configuration from the Web InterfaceConfiguring the IP Address Options Options for Configuring the IP Address and MaskConfiguring the Ethernet Interface with DPA-Remote ProcedureStarting Point Configuring the IP Address Using Ping-ARP Configuring an IP Address using Dhcp and Rarp Configuring the Ethernet Interface from the Command LineManual Configuration Procedure Manual Configuration ExampleConfiguring an IP Address using Dhcp and Rarp Configuring Ports for RealPort Configuring the RealPort Software What is RealPort?Configuration Options About RealPortConfiguring Ports Web Interface Example Configuring Ports for RealPort Command LineConfiguring Ports for Printers Configuration Considerations Configuring Printer Connections Command Line Configuring Ports for Printers Web InterfaceTips for telnet and rsh Printing Related InformationConfiguring Printer Connections Command Line Configuring a Port for Direct-Access Printing Configuring a Port for Direct-Access Printing Configuring Ports for Terminals Configuring Ports for Terminals Web Interface Configuring Ports for Terminals Command LinePort Defaults About Computer Connections Configuring Typical PC ConnectionsAbout Computer Connections Configuring Ports for Modems Tips on Configuring a Modem Configuring Ports for Modems Web Interface Before You Begin Configuring PPP Configuring PPP Connections Web Interface Configuring Inbound PPP Connections Command Line Configuring Inbound PPP Connections Example Configuring Outbound PPP Connections Command Line Set user name=name n1=telephone-number Configuring IP Routing What is Routing Introduction to RoutingTypes of Routing About RIP Routing Updates PortServer TS 8/16 Participation in RIP Updates Configuring Static Routes Example Route Using the Ethernet InterfaceExample Route Using a PPP Link Example Dynamic Routes Configuring Dynamic Routes Using RIPConfiguring Proxy ARP Configuring Proxy ARP Configuring Autoconnection Configuring a Port for Autoconnection Web Interface Configuring Autoconnection By Port Command LineAbout Autoconnection Configuring a User for Autoconnection Command Line Configuring a User for Autoconnection Web InterfaceConfiguring a User for Autoconnection Command Line Configuring Console Management Configuring Console Management Web Interface Configuring Console Management Command LineAbout Console Management Example Alternate IP Addresses Example SSH2 and Menu Access10-4 Configuring Security Features Controlling Access to Inbound Ports Controlling Access to the PortServer TS 8/16 ConfigurationControlling Access to the PortServer TS 8/16 Command Line Controlling Access to Outbound PortsWhat is RADIUS? Using Radius to Authenticate UsersRadius Components Radius Table KeyConfiguring Radius Web Interface Radius Accounting Attributes RFCHow Radius Works Radius Command Line Configuration Example Configuring Radius Command LineIssuing User Passwords Configuring SSH Version 2 for Secure Communication Password ProtectionUsing a Public Key Configuring DNS About the Domain Name System Configuration Procedures Procedure for Using a Name ServerProcedure for Using a Host File 13-4 Configuring Snmp About Snmp and the PortServer TS 8/16 Agent Configuration Procedure Web Interface Configuration Procedure Command LineConfiguration Example 14-4 Managing the OS and Configuration Upgrading the OS Firmware Web Interface Prerequisite Task Upgrading the OS Firmware Command LineWhen To Use Remote Configuration Configuring PortServer TS 8/16 from a Remote HostRules for Editing a Configuration file Copying the Configuration File to a HostCpconf fromhost=199.250.121.12cnfg-fle Radius Resetting the Configuration to DefaultsConfiguring Users About Configuring Users Common User FeaturesConfiguration Methods Configuring a User Web Interface Configuring a User Command Line Examples Configuration Examples Configuration Terminal Server Configuration Without RealPortConfiguration Notes IllustrationTerminal Server Configuration Using Autoconnection Terminal Server Configuration Using RealPort Dial-In PPP Connection Using Radius Dial-In PPP Connection Using Radius PortServer TS 8/16 Troubleshooting Introduction Symptom PortServer TS 8/16 Does Not BootAssumptions Symptom Cannot Telnet to the PortServer TS 8/16Running PortServer TS 8/16 Hardware Diagnostics Symptom Trouble Accessing a PortProcedure Running the Post Using the LEDs Procedure Running the Post from a TerminalRunning PortServer TS 8/16 Post Verifying Tftp on a Unix System Troubleshooting Tftp ProblemsResetting PortServer TS 8/16 Configuration to Defaults Command Line ProcedureFront Panel Procedure Verifying the PortServer TS 8/16 IP Address 17-9 Checking for Duplicate IP Addresses Pinging an IP Address Verifying the Network Cabling AIX Verifying the RealPort Process Verifying the RealPort ProcessHP-UX Verifying the RealPort Process Linux Verifying the RealPort ProcessWindows NT Verifying the RealPort Service Windows 2000 Verifying the RealPort ServiceSolaris Verifying the RealPort Process RealPort Checking and Changing Port ConfigurationDigi International Bren Road East Minnetonka, MN Digi Contact Information

16, TS8 specifications

The Digi TS8 and TS16 are advanced devices within the Digi TransPort series, which are renowned for their versatility in providing robust network connectivity solutions. Designed to cater to the needs of IoT (Internet of Things) applications, these routers are excellent for businesses that require reliable, high-performance communication across various environments.

One of the standout features of the Digi TS8 and TS16 is their cellular connectivity. Both models support multiple cellular bands, including 4G LTE, ensuring that users can maintain a stable and fast internet connection even in remote locations. This makes them ideal for applications like smart grid management, digital signage, and industrial telemetry, where constant connectivity is crucial.

Another significant aspect of the Digi TS8 and TS16 is their dual SIM capability. This feature allows for seamless failover between two cellular networks. In cases where one network experiences an outage, the device automatically switches to the secondary network, thus minimizing downtime and maintaining business continuity. This redundancy is a vital characteristic for mission-critical applications.

The routers also support various WAN technologies, including LTE, Ethernet, and Wi-Fi, providing flexibility for diverse deployment scenarios. With their comprehensive networking capabilities, the Digi TS8 and TS16 can be integrated into existing infrastructures with ease.

In terms of security, these devices offer a robust suite of features designed to safeguard data. They come equipped with advanced firewall capabilities, VPN support, and secure tunneling protocols, ensuring that data transmitted across the network remains protected against unauthorized access.

Additionally, management and monitoring are made easy with Digi’s intuitive web interface and cloud management platform. Users can remotely configure, monitor, and manage their devices, enabling efficient performance tracking and troubleshooting from anywhere in the world.

Both the Digi TS8 and TS16 are built to endure harsh environmental conditions, boasting an industrial-grade design that adheres to rigorous standards. They can operate effectively in extreme temperatures and are resistant to dust and moisture, making them suitable for outdoor and rugged deployments.

Overall, the Digi TS8 and TS16 provide an extensive set of features and characteristics that address the growing demands of modern connectivity. Their reliability, security, and flexible deployment options make them a preferred choice for businesses looking to harness the power of IoT technology. Whether for industrial applications or remote site management, these devices lead the market with their performance and adaptability.