Home > Articles > Software Development & Management

Like this article? We recommend

Like this article? We recommend

Migrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX MigrationsMigrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX Migrations

Learn More Buy

Like this article? We recommend

Like this article? We recommend

Migrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX MigrationsMigrating to the Solaris Operating System: The Discipline of UNIX-to-UNIX Migrations

Learn More Buy

Layer 3—RIP Network Redundancy

The Routing Information Protocol (RIP) is based on the Bellman-Ford distance vector algorithm. The idea behind the RIP is that each RIP router builds a one-dimensional array that contains a scalar notion of hops, to reach all other hops. (OSPF was able to more accurately use the notion of cost, which could capture information such as link speed.) RIP routers flood each other with their view of the network by first starting with directly connected neighbor routers, then modifying their vector if they find from peer updates that there is a shorter path.

After a few updates, a complete routing table is constructed. When a router detects a failure, the distance is updated to infinity. Ideally, all routers would eventually receive the proper update and adjust their tables accordingly. However, if the network is designed with redundancy, there can be issues in properly updating the tables to reflect a failed link. There are problems such as count to infinity and split horizon, which have various fixes to this protocol. The RIP was a first implementation of the distance vector algorithm. The RIPv2, the most common, addresses scalability and other limitations of the RIP.

To better understand the failover capabilities of RIPv2, the following test network was set up, shown in FIGURE 16.

Figure 16FIGURE 16 RIP Network Setup

CODE EXAMPLE 10 shows the server-to-client path before node failure. The highlighted lines show the path through the switch sw3.

CODE EXAMPLE 10 Server-to-Client Path Before Node Failure 

server># traceroute client 
traceroute: Warning: Multiple interfaces found; using 11.0.0.51 @ hme0
traceroute to client (16.0.0.51), 30 hops max, 40 byte packets
 1 11.0.0.1 (11.0.0.1) 0.711 ms 0.524 ms 0.507 ms
 2 12.0.0.2 (12.0.0.2) 1.448 ms 0.919 ms 0.875 ms
 3 13.0.0.2 (13.0.0.2) 1.304 ms 0.977 ms 0.964 ms
 4 14.0.0.2 (14.0.0.2) 1.963 ms 1.091 ms 1.151 ms
 5 15.0.0.2 (15.0.0.2) 1.158 ms 1.059 ms 1.037 ms
 6 client (16.0.0.51) 1.560 ms 1.170 ms 1.107 ms

The following code examples show the initial routing tables. The highlighted line in CODE EXAMPLE 11 shows the path to the client through the switch sw3.

CODE EXAMPLE 11 Switch sw1 Initial Routing Table

 OR Destination    Gateway     Mtr  Flags   Use M-Use VLAN   Acct-1
*s 10.100.0.0/24   12.0.0.1     1 UG---S-um  32   0 net12  0   
*r 11.0.0.0/8     12.0.0.1     2 UG-----um  15   0 net12  0   
*d 12.0.0.0/8     12.0.0.2     1 U------u-  184   0 net12  0   
*d 13.0.0.0/8     13.0.0.1     1 U------u-  52   0 net13  0   
*r 14.0.0.0/8     13.0.0.2     2 UG-----um   1   0 net13  0   
*r 15.0.0.0/8     18.0.0.2     3 UG-----um   0   0 net18  0   
*r 16.0.0.0/8     13.0.0.2     4 UG-----um  10   0 net13  0   
*r 17.0.0.0/8     18.0.0.2     2 UG-----um   0   0 net18  0   
*d 18.0.0.0/8     18.0.0.1     1 U------u-  12   0 net18  0   
*d 127.0.0.1/8    127.0.0.1     0 U-H----um   0   0 Default 0

CODE EXAMPLE 12 Switch sw2 Initial Routing Table

sw2:3 # sh ipr

 OR Destination    Gateway     Mtr  Flags   Use M-Use VLAN   Acct-1
*s 10.100.0.0/24   18.0.0.1     1 UG---S-um  81   0 net18  0   
*r 11.0.0.0/8     18.0.0.1     3 UG-----um   9   0 net18  0   
*r 12.0.0.0/8     18.0.0.1     2 UG-----um  44   0 net18  0   
*r 13.0.0.0/8     18.0.0.1     2 UG-----um   0   0 net18  0   
*r 14.0.0.0/8     17.0.0.2     2 UG-----um   0   0 net17  0   
*r 15.0.0.0/8     17.0.0.2     2 UG-----um   0   0 net17  0   
*r 16.0.0.0/8     17.0.0.2     3 UG-----um   3   0 net17  0   
*d 17.0.0.0/8     17.0.0.1     1 U------u-  17   0 net17  0   
*d 18.0.0.0/8     18.0.0.2     1 U------u-  478   0 net18  0 
*d 127.0.0.1/8    127.0.0.1     0 U-H----um   0   0 Default 0 
#
#

CODE EXAMPLE 13 Switch sw3 Initial Routing Table

sw3:3 # sh ipr

 OR Destination    Gateway     Mtr  Flags   Use M-Use VLAN   Acct-1
*s 10.100.0.0/24   13.0.0.1     1 UG---S-um  79   0 net13  0   
*r 11.0.0.0/8     13.0.0.1     3 UG-----um   3   0 net13  0   
*r 12.0.0.0/8     13.0.0.1     2 UG-----um  44   0 net13  0   
*d 13.0.0.0/8     13.0.0.2     1 U------u-  85   0 net13  0   
*d 14.0.0.0/8     14.0.0.1     1 U------u-  33   0 net14  0   
*r 15.0.0.0/8     14.0.0.2     2 UG-----um   0   0 net14  0   
*r 16.0.0.0/8     14.0.0.2     3 UG-----um  10   0 net14  0   
*r 17.0.0.0/8     14.0.0.2     2 UG-----um   0   0 net14  0   
*r 18.0.0.0/8     13.0.0.1     2 UG-----um   0   0 net13  0   
*d 127.0.0.1/8    127.0.0.1     0 U-H----um   0   0 Default 0

The highlighted line in CODE EXAMPLE 14 shows the path to the server through the switch sw3.

CODE EXAMPLE 14 Switch sw4 Initial Routing Table

sw4:7 # sh ipr

 OR Destination    Gateway     Mtr  Flags   Use M-Use VLAN   Acct-1
*s 10.100.0.0/24   14.0.0.1     1 UG---S-um  29   0 net14  0   
*r 11.0.0.0/8     14.0.0.1     4 UG-----um   9   0 net14 
*r 12.0.0.0/8     14.0.0.1     3 UG-----um   0   0 net14 0   
*r 13.0.0.0/8     14.0.0.1     2 UG-----um   0   0 net14  0   
*d 14.0.0.0/8     14.0.0.2     1 U------u-  13   0 net14  0   
*d 15.0.0.0/8     15.0.0.1     1 U------u-  310   0 net15  0   
*r 16.0.0.0/8     15.0.0.2     2 UG-----um  16   0 net15  0   
*d 17.0.0.0/8     17.0.0.2     1 U------u-   3   0 net17  0   
*r 18.0.0.0/8     17.0.0.1     2 UG-----um   0   0 net17  0   
*d 127.0.0.1/8    127.0.0.1     0 U-H----um   0   0 Default 0

The highlighted lines in the following output from running the traceroute client command show the new path from the server to the client through switch sw2 after switch sw3 fails.

server># traceroute client
traceroute: Warning: Multiple interfaces found; using 11.0.0.51 @ hme0
traceroute to client (16.0.0.51), 30 hops max, 40 byte packets
 1 11.0.0.1 (11.0.0.1) 0.678 ms 0.479 ms 0.465 ms
 2 12.0.0.2 (12.0.0.2) 1.331 ms 0.899 ms 0.833 ms
 3 18.0.0.2 (18.0.0.2) 1.183 ms 0.966 ms 0.953 ms 
 4 17.0.0.2 (17.0.0.2) 1.379 ms 1.082 ms 1.062 ms
 5 15.0.0.2 (15.0.0.2) 1.101 ms 1.024 ms 0.993 ms
 6 client (16.0.0.51) 1.209 ms 1.086 ms 1.074 ms

The following output shows the server pings.

64 bytes from client (16.0.0.51): icmp_seq=18. time=2. ms
64 bytes from client (16.0.0.51): icmp_seq=19. time=2. ms
64 bytes from client (16.0.0.51): icmp_seq=20. time=2. ms
ICMP Net Unreachable from gateway 12.0.0.2
 for icmp from server (11.0.0.51) to client (16.0.0.51)
ICMP Net Unreachable from gateway 12.0.0.2
..
..
for icmp from server (11.0.0.51) to client (16.0.0.51)
ICMP Net Unreachable from gateway 12.0.0.2
 for icmp from server (11.0.0.51) to client (16.0.0.51)
ICMP Net Unreachable from gateway 12.0.0.2
 for icmp from server (11.0.0.51) to client (16.0.0.51)
64 bytes from client (16.0.0.51): icmp_seq=41. time=2. ms
64 bytes from client (16.0.0.51): icmp_seq=42. time=2. ms
64 bytes from client (16.0.0.51): icmp_seq=43. time=2. ms

The fault detection and recovery took in excess of 21 seconds. The RIPv2 is widely available, however, the failure detection and recovery is not optimal. Further, there are other inherent robustness issues with the RIP.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020