How Split Horizon Affects RIP/IGRP Routing Updates when Secondary Addresses Are Involved

Available Languages

Updated:August 18, 2005
Document ID:13712

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

A router configured with a primary IP address and secondary addresses on a given interface behave differently when you send updates out that interface depending on whether split horizon is enabled or disabled. This document provides tables that list the differences in the updates.

Note: Source interface is defined as the network interface on which the update is sent.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Tables

Table 1: RIP updates with secondary address on different major network than primary

Split horizon Update source Update contents
Enabled Primary Subnets of primary (if known through non-source interfaces). Other major networks (including secondary network), known through non-source interface, summarized to major net boundary.
Enabled Secondary Subnets of secondary (if known through non-source interface). Other major networks (including primary network), known through non-source interface, summarized to major net boundary.
Disabled Primary All known subnets of primary. Other major networks (including secondary network), summarized to major net boundary.
Disabled Secondary All known subnets of secondary. Other major networks (including primary network), summarized to major net boundary.

Table 2: RIP updates with secondary address on same major network as primary

Split horizon Update source Update contents
Enabled Primary Subnets of primary/secondary (if known through non-source interfaces). Other major networks, known through non-source interface, summarized to major net boundary.
Enabled Secondary None - no updates sourced from secondary.
Disabled Primary All known subnets of primary/secondary. Other major networks summarized to major net boundary.
Disabled Secondary All known subnets of primary/secondary. Other major networks summarized to major net boundary.

Table 3: IGRP updates with secondary address on different major network than primary

Split horizon Update source Update contents
Enabled Primary Subnets of primary (if known through non-source interfaces). Other major networks (including secondary network), known through non-source interface, summarized to major net boundary.
Enabled Secondary Only subnets of secondary network.
Disabled Primary All known subnets of primary. Other major networks (including secondary network), summarized to major net boundary.
Disabled Secondary All known subnets of secondary. Other major networks (including primary network), summarized to major net boundary.

Table 4: IGRP updates with secondary address on same major network as primary

Split horizon Update source Update contents
Enabled Primary Subnets of primary/secondary (if known through non-source interfaces). Other major networks, known through non-source interface, summarized to major net boundary.
Enabled Secondary None - No updates source from secondary.
Disabled Primary All known subnets of primary/secondary. Other major networks summarized to major net boundary.
Disabled Secondary All known subnets of primary/secondary. Other major networks summarized to major net boundary.

Split horizon is enabled on each interface by default. In order to disable split horizon, use the no ip split-horizon interface subcommand as shown here:

int e 0
no ip split-horizon

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products