Skip to main content

Eigrp stub

Configuring EIGRP Stub Routing

To configure a remote or spoke router for EIGRP stub routing, use the following commands beginning in router configuration mode:


Command
Purpose

Step 1

router(config)# router eigrp as-number

Configures a remote or distribution router to run an EIGRP process.

Step 2

router(config-router)# network network-number

Specifies the network address of the EIGRP distribution router.

Step 3

router(config-router)# eigrp stub [receive-only | connected | static | summary]

Configures a remote router as an EIGRP stub router.

Verifying EIGRP Stub Routing

To verify that a remote router has been configured as a stub router with the EIGRP Stub Routing feature, use the show ip eigrp neighbor detail command from the distribution router in privileged EXEC mode. The last line of the output will show the stub status of the remote or spoke router. The following example output is from the show ip eigrp neighbor detail command:

router# show ip eigrp neighbor detail

IP-EIGRP neighbors for process 1

H Address Interface Hold Uptime SRTT RTO Q Seq Type

(sec) (ms) Cnt Num

0 10.1.1.2 Se3/1 11 00:00:59 1 4500 0 7

Version 12.1/1.2, Retrans: 2, Retries: 0

Stub Peer Advertising ( CONNECTED SUMMARY ) Routes

Monitoring and Maintaining EIGRP Stub Routing

To enable EIGRP stub packet debugging, use the following command in privileged EXEC mode:


Command
Purpose

Router# debug eigrp packet stub

Displays debug information about the stub status of peer routers.


Configuration Examples

A router that is configured as a stub with the eigrp stub command shares connected and summary routing information with all neighbor routers by default. Four optional keywords can be used with the eigrp stub command to modify this behavior:

•receive-only

•connected

•static

•summary

This section provides configuration examples for all forms of the eigrp stub command. The eigrp stub command can be modified with several options, and these options can be used in any combination except for the receive-only keyword. The receive-only keyword will restrict the router from sharing any of its routes with any other router in that EIGRP autonomous system, and the receive-only keyword will not permit any other option to be specified because it prevents any type of route from being sent. The three other optional keywords (connected, static, and summary) can be used in any combination but cannot be used with the receive-only keyword. If any of these three keywords is used individually with the eigrp stub command, connected and summary routes will not be sent automatically.

The connected keyword will permit the EIGRP Stub Routing feature to send connected routes. If the connected routes are not covered by a network statement, it may be necessary to redistribute connected routes with the redistribute connected command under the EIGRP process. This option is enabled by default.

The static keyword will permit the EIGRP Stub Routing feature to send static routes. Without the configuration of this option, EIGRP will not send any static routes, including internal static routes that normally would be automatically redistributed. It will still be necessary to redistribute static routes with the redistribute static command.

The summary keyword will permit the EIGRP Stub Routing feature to send summary routes. Summary routes can be created manually with the summary address command or automatically at a major network border router with the auto-summary command enabled. This option is enabled by default.

In the following example, the eigrp stub command is used to configure the router as a stub that advertises connected and summary routes: 

router eigrp 1
network 10.0.0.0
eigrp stub

In the following example, the eigrp stub command is issued with the connected and static keywords to configure the router as a stub that advertises connected and static routes (sending summary routes will not be permitted): 

router eigrp 1
network 10.0.0.0
eigrp stub connected static

In the following example, the eigrp stub command is issued with the receive-only keyword to configure the router as a receive-only neighbor (Connected, summary, and static routes will not be sent): 

router eigrp 1
network 10.0.0.0 eigrp
eigrp stub receive-only

Command Reference

This section documents the eigrp stub command. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command reference publications.

eigrp stub

To configure a router as a stub using Enhanced Interior Gateway Routing Protocol (EIGRP), use the eigrp stub command in router configuration mode. To disable the EIGRP Stub Routing feature, use the no form of this command.

eigrp stub [receive-only | connected | static | summary]

no eigrp stub [receive-only | connected | static | summary]

Syntax Description

receive-only

(optional) Sets the router as a receive-only neighbor.

connected

(optional) Advertises connected routes.

static

(optional) Advertises static routes.

summary

(optional) Advertises summary routes.


Defaults

Stub routing is not enabled by default.

Command Modes

Router configuration

Command History
Release
Modification

12.0(7)T

This command was introduced.

12.0(15)S

This command was integrated into Cisco IOS Release 12.0(15)S.


Usage Guidelines

Use the eigrp stub command to configure a router as a stub where the router directs all IP traffic to a distribution router.

The eigrp stub command can be modified with several options, and these options can be used in any combination except for the receive-only keyword. The receive-only keyword will restrict the router from sharing any of its routes with any other router in that EIGRP autonomous system, and the receive-only keyword will not permit any other option to be specified because it prevents any type of route from being sent. The three other optional keywords (connected, static, and summary) can be used in any combination but cannot be used with the receive-only keyword. If any of these three keywords is used individually with the eigrp stub command, connected and summary routes will not be sent automatically.

The connected keyword will permit the EIGRP Stub Routing feature to send connected routes. If the connected routes are not covered by a network statement, it may be necessary to redistribute connected routes with the redistribute connected command under the EIGRP process. This option is enabled by default.

The static keyword will permit the EIGRP Stub Routing feature to send static routes. Without the configuration of this option, EIGRP will not send any static routes, including internal static routes that normally would be automatically redistributed. It will still be necessary to redistribute static routes with the redistribute static command.

The summary keyword will permit the EIGRP Stub Routing feature to send summary routes. Summary routes can be created manually with the summary address command or automatically at a major network border router with the auto-summary command enabled. This option is enabled by default.

Note Multi-access interfaces, such as ATM, Ethernet, Frame Relay, ISDN PRI, and X.25, are supported by the EIGRP Stub Routing feature only when all routers on that interface, except the hub, are configured as stub routers.

Examples

In the following example, the eigrp stub command is used to configure the router as a stub that advertises connected and summary routes: 

router eigrp 1
network 10.0.0.0
eigrp stub

In the following example, the eigrp stub command is issued with the connected and static keywords to configure the router as a stub that advertises connected and static routes (sending summary routes will not be permitted): 

router eigrp 1
network 10.0.0.0
eigrp stub connected static

In the following example, the eigrp stub command is issued with the receive-only keyword to configure the router as a receive-only neighbor (Connected, summary, and static routes will not be sent): 

router eigrp 1
network 10.0.0.0 eigrp

eigrp stub receive-only

Comments

Post a Comment

Popular posts from this blog

LSA types. Type Code

LSA types. Type Code Description 1 Router LSA 2 Network LSA 3 Network Summary LSA 4 ASBR Summary LSA 5 AS External LSA 6 Group Membership LSA 7 NSSA External LSA 8 External Attributes LSA 9 Opaque LSA (link-local scope) 10 Opaque LSA (area-local scope) 11 Opaque LSA (AS scope)
Post a Comment
Read more

OSPF STUB , NSSA AREAs

IP Routing How Does OSPF Generate Default Routes? Document ID: 13692 Contents Introduction Before You Begin Conventions Prerequisites Components Used Types of OSPF Areas Normal Areas Stub and Totally Stub Areas NSSAs Related Information Introduction The way that Open Shortest Path First (OSPF) generates and advertises default routes (0.0.0.0) varies depending on the type of area the default route is being injected into. In this document, we cover normal areas, stub/totally stub areas and not-so-stubby areas (NSSAs). Before You Begin Conventions For more information on document conventions, refer to the Cisco Technical Tips Conventions . Prerequisites There are no specific prerequisites for this document. Components Used This document is not restricted to specific software and hardware versions. Types of OSPF Areas Normal Areas: These areas can either be standard areas or transit (backbone) areas. Standard areas are defined as ...
Post a Comment
Read more

IP prefix-list

IP prefix-list ip prefix-list provides the most powerful prefix based filtering mechanism Here is a quick little tutorial on Prefix-lists for you. A normal access-list CANNOT check the subnet mask of a network. It can only check bits to make sure they match, nothing more. A prefix-list has an advantage over an access-list in that it CAN check BOTH bits and subnet mask - both would have to match for the network to be either permitted or denied. For checking bits a prefix list ALWAYS goes from left to right and CANNOT skip any bits. A basic example would be this: 172.16.8.0/24 If there is only a / after the network (no le or ge) then the number after the / is BOTH bits checked and subnet mask. So in this case it will check the 24 bits from left to right (won't care about the last 8 bits) AND it will make sure that it has a 24 bit mask. BOTH the 24 bits checked and the 24 bit subnet mask must match for the network to be permitted or denied. No we can do a range of subn...
Post a Comment
Read more