Eigrp Routing IP Service and IPbase

Hello all,

Can anybody advise if it is possible to use Eigrp routing on IPbase Version 15.0. It would seem that Cisco does not support full Eigrp routing on the IPbase IOS and an upgrade to IP services is required. I was supposed to be replacing two 12 port 3750 Core switches with two 3750-X 48 port switches. They came loaded with the IPbase version 15.0 which mean't that routing did not work. I don't think the extra £6000 to upgrade to IPservices will go down well with the customer. I have to present a few options on how we can faciltate the upgrade. These are the options my prefered option would be number 1. I dont this this will happen so I may have to come up with way to route traffic using another method

1. Customer pays for IPservice IOS and upgrade goes forward as planned
2.Remove eigrp and use static routing with floating statics
3. Eigrp Stub not sure if this is possible but this means we could use the IPbase IOS. My understanding is that with stub routing the stub router can be configured to redistrubute networks but will not talk to other routers about networks its learned. My thoughts would be then can I not just ensure all the networks that would normallly be learned by Eigrp are redistubuted.

By the way the network has a Core Access and server layer. Behind the Access and Server layers are several networks. Here is a print out from Core A switch. If anyone has any ideas or thoughts it would be much appreciated

TMSNBS-CORE-A#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.248.238.13 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 23 subnets, 8 masks
D 10.248.236.28/30 [90/1792] via 10.248.236.18, 1w3d, Port-channel5
[90/1792] via 10.248.236.10, 1w3d, Port-channel3
D EX 10.248.241.0/24 [170/3328] via 10.248.238.3, 1w3d, Vlan10
[170/3328] via 10.248.236.10, 1w3d, Port-channel3
D 10.248.236.24/30 [90/3072] via 10.248.238.3, 1w3d, Vlan10
[90/3072] via 10.248.236.10, 1w3d, Port-channel3
[90/3072] via 10.248.236.2, 1w3d, Port-channel1
D 10.248.236.20/30 [90/1792] via 10.248.236.10, 1w3d, Port-channel3
S 10.248.239.16/28 [1/0] via 10.248.239.13
C 10.248.236.16/30 is directly connected, Port-channel5
C 10.248.236.12/30 is directly connected, Port-channel4
D 10.248.224.0/22 [90/3072] via 10.248.236.2, 1w3d, Port-channel1
C 10.248.236.8/30 is directly connected, Port-channel3
D 10.248.228.0/22 [90/3328] via 10.248.238.3, 1w3d, Vlan10
[90/3328] via 10.248.236.10, 1w3d, Port-channel3
D 10.248.234.0/23 [90/3072] via 10.248.236.14, 1w3d, Port-channel4
C 10.248.236.4/30 is directly connected, Port-channel2
D 10.248.232.0/23 [90/3072] via 10.248.236.18, 1w3d, Port-channel5
C 10.248.238.0/28 is directly connected, Vlan10
C 10.248.239.0/28 is directly connected, Vlan110
C 10.248.236.0/30 is directly connected, Port-channel1
D EX 10.248.237.0/29 [170/3072] via 10.248.236.18, 1w3d, Port-channel5
[170/3072] via 10.248.236.14, 1w3d, Port-channel4
S 10.248.238.48/28 [1/0] via 10.248.238.13
S 10.248.238.32/28 [1/0] via 10.248.238.13
D 10.248.236.32/30 [90/1792] via 10.248.236.14, 1w3d, Port-channel4
[90/1792] via 10.248.236.10, 1w3d, Port-channel3
D 10.248.236.126/32 [90/129536] via 10.248.236.10, 1w3d, Port-channel3
C 10.248.236.125/32 is directly connected, Loopback0
S 10.248.236.128/25 [1/0] via 10.248.238.13
S* 0.0.0.0/0 [1/0] via 10.248.238.13

Find more posts tagged with

Save $250 on 2025 certification boot camps from Infosec!

Book now with code EOY2025

Button

Comments

mattau

as a side note, why does it cost so much to go from ipbase to ipservices? is there special hardware requirements on the ipservices switch? or is it just a licensing thing?

Monkerz

https://supportforums.cisco.com/docs/DOC-3362

This link may help.

As a side note, I found out a few months ago that a 3750 running ipbase sure does allow OSPF, but there is a limit on how many OSPF routes it allows in the routing table.

unclerico

Your understanding of EIGRP stub routing is correct; if your stub is adjacent to multiple devices it will not redistribute/reflect the routes learned from one to the other. You have a few options on how to get the routes from the stub into the full EIGRP backbone, but if you are talking about putting these devices in the core then you don't want stub routing there. Static routes suck especially if the addressing isn't hierarchical in nature which requires more manual administration which inevitably leads to user error; however, from the looks of your routing table the addressing space looks pretty good. If the customer isn't willing to foot the extra 6k for the license upgrade, then your options are convert to OSPF or RIP, or use static routes. As monkerz says, OSPF in this situation is extremely scaled back and limits the number or dynamically learned routes, but it could be an option.

jason_lunde

Monkerz wrote: »

https://supportforums.cisco.com/docs/DOC-3362

This link may help.

As a side note, I found out a few months ago that a 3750 running ipbase sure does allow OSPF, but there is a limit on how many OSPF routes it allows in the routing table.

^ this. if its not to hard switch to ospf. IP base will support one process and up to 200 routes, which looks like will cover what you have there.

xXErebuS

cjthedj45 wrote: »

Hello all,

Can anybody advise if it is possible to use Eigrp routing on IPbase Version 15.0. It would seem that Cisco does not support full Eigrp routing on the IPbase IOS and an upgrade to IP services is required. I was supposed to be replacing two 12 port 3750 Core switches with two 3750-X 48 port switches. They came loaded with the IPbase version 15.0 which mean't that routing did not work. I don't think the extra £6000 to upgrade to IPservices will go down well with the customer. I have to present a few options on how we can faciltate the upgrade. These are the options my prefered option would be number 1. I dont this this will happen so I may have to come up with way to route traffic using another method

1. Customer pays for IPservice IOS and upgrade goes forward as planned
2.Remove eigrp and use static routing with floating statics
3. Eigrp Stub not sure if this is possible but this means we could use the IPbase IOS. My understanding is that with stub routing the stub router can be configured to redistrubute networks but will not talk to other routers about networks its learned. My thoughts would be then can I not just ensure all the networks that would normallly be learned by Eigrp are redistubuted.

By the way the network has a Core Access and server layer. Behind the Access and Server layers are several networks. Here is a print out from Core A switch. If anyone has any ideas or thoughts it would be much appreciated

TMSNBS-CORE-A#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.248.238.13 to network 0.0.0.0

10.0.0.0/8 is variably subnetted, 23 subnets, 8 masks
D 10.248.236.28/30 [90/1792] via 10.248.236.18, 1w3d, Port-channel5
[90/1792] via 10.248.236.10, 1w3d, Port-channel3
D EX 10.248.241.0/24 [170/3328] via 10.248.238.3, 1w3d, Vlan10
[170/3328] via 10.248.236.10, 1w3d, Port-channel3
D 10.248.236.24/30 [90/3072] via 10.248.238.3, 1w3d, Vlan10
[90/3072] via 10.248.236.10, 1w3d, Port-channel3
[90/3072] via 10.248.236.2, 1w3d, Port-channel1
D 10.248.236.20/30 [90/1792] via 10.248.236.10, 1w3d, Port-channel3
S 10.248.239.16/28 [1/0] via 10.248.239.13
C 10.248.236.16/30 is directly connected, Port-channel5
C 10.248.236.12/30 is directly connected, Port-channel4
D 10.248.224.0/22 [90/3072] via 10.248.236.2, 1w3d, Port-channel1
C 10.248.236.8/30 is directly connected, Port-channel3
D 10.248.228.0/22 [90/3328] via 10.248.238.3, 1w3d, Vlan10
[90/3328] via 10.248.236.10, 1w3d, Port-channel3
D 10.248.234.0/23 [90/3072] via 10.248.236.14, 1w3d, Port-channel4
C 10.248.236.4/30 is directly connected, Port-channel2
D 10.248.232.0/23 [90/3072] via 10.248.236.18, 1w3d, Port-channel5
C 10.248.238.0/28 is directly connected, Vlan10
C 10.248.239.0/28 is directly connected, Vlan110
C 10.248.236.0/30 is directly connected, Port-channel1
D EX 10.248.237.0/29 [170/3072] via 10.248.236.18, 1w3d, Port-channel5
[170/3072] via 10.248.236.14, 1w3d, Port-channel4
S 10.248.238.48/28 [1/0] via 10.248.238.13
S 10.248.238.32/28 [1/0] via 10.248.238.13
D 10.248.236.32/30 [90/1792] via 10.248.236.14, 1w3d, Port-channel4
[90/1792] via 10.248.236.10, 1w3d, Port-channel3
D 10.248.236.126/32 [90/129536] via 10.248.236.10, 1w3d, Port-channel3
C 10.248.236.125/32 is directly connected, Loopback0
S 10.248.236.128/25 [1/0] via 10.248.238.13
S* 0.0.0.0/0 [1/0] via 10.248.238.13

Base supports RIP; just redistribute at a boundary. In addition, the 3750X-S supports more than the 3750-S; I would verify with your rep...

clamz

Hey you should still be able to advertise routes with the stub configuration:

SOLUTIONS
There are several solutions to some of the aforementioned problems:
• Add a redundant Ethernet link between routers A and B to contain the backbone traffic to the hub site
• Use some level of route summarization to limit the extents of the EIGRP QUERY mechanism.
• Configure a distribute-list to limit the networks advertised by the spoke routers.
However, the best solution is to provide a means within the context of the EIGRP protocol itself to control traffic flows and limit query depth. The EIGRP Stub Router functionality in Cisco IOS Software Release 12.0(7)T can achieve this solution.
In the EIGRP HELLO packet, which is used to establish adjacencies between EIGRP neighbors, a new Type-Length-Value (TLV) field has been added which allows a router to designate itself as a stub router. A stub router will only advertise the availability of a limited set of configured routes, rather than the entire routing table. The syntax for configuring an EIGRP stub router is:
eigrp stub [ [receive-only] || [connected] [static] [summary] [redistributed] ]
The following options are available:
• Receive-only: router only accepts, but does not explicitly advertise, any routes. This option may not be used in combination with any other options.
• Connected: router advertises directly-connected networks
• Static: router advertises any configured static routes
• Summary: router advertises any configured summarized routes
• Redistributed: router advertises any routes learned from another protocol, such as OSPF

However the only thing is QUERY packets will not go to the 3750x's.. If you configure receive-only then the stub router will not advertise anything.. This shouldn't be a problem for you and should save the $5k license fee.

cjthedj45

Hi Thanks for all your responses. We are waiting for the customer to make a desicion. I have presented the option so need to see what they say. I agree that using statics will be a bit of a backward step and difficult to implement. Hopefully the customer will suck up the 6k cost and I can stick with the original plan.