RE: IGRP and EIGRP metric [7:66522]

2003-03-31 Thread Priscilla Oppenheimer
Priscilla Oppenheimer wrote:
 
 Tim Champion  wrote in message 
 news:[EMAIL PROTECTED] 
  When calculating the metric of an IGRP route (with
 non-default 'K' values)
  which load and reliability values does one use? Do you use
 the highest,
  lowest or average value for the entire route? 

Load and reliability are cumulative as far as I can tell. That is, they
reflect the load and reliability for the entire path. That's what Doyle says
and I now believe him. :-) You can test it without even messing with the K
values. To see the reported load and reliability, use a protcol anzlyer, or,
even easier: do a show ip route with the network of choice as a parameter.
The info is shared and saved even, if it's not used to calculate the
composite metric.

  
  Also if anyone could point me to a document on the above it
 would be
  appreciated. 
  
  
  Many thanks in advance. 

I did some testing. It was impossible to come up with a testing methodology
that would give a conclusive result, especially considering the limitations
of my lab, and the limitations of the protcols, but I'm pretty sure that
both load and reliability are cumulative. Well, for reliabiity, the error
rate is cummulative really. And load does seem to be somewhat smart about
different bandwidths. It can't be too smart since it only knows the lowest
bandwdith for the path, but it seems to take this into account along with
the bandwidth for its interfaces, which is necessary for a cumulative load
to mean anything.

Needless, to say, the real answer is don't even bother with reliabilty and
load as IGRP or EIGRP metrics. With a 90-second update timer (IGRP) and
nonperiodic, partial, and bounded updates for EIGRP, the protocol can't
possibly keep accurate track of the sampling that interfaces do every 5
seconds to determine the load and reliability.

It's kind of weird that Cisco let these two opposing goals end up in the
protocol:

* Low bandwidth usage by the protocol (infrequent updates)
* Path selection based on quickly-changing load and reliabity metrics

Well, probably nobody cares (and rightly so! ;-) But it was bothering me
that the original poster never got a good answer.

Priscilla

 
 Remember this oldie but goodie question? Most of the answers
 were links to papers that don't answer the question. I answered
 the question by saying that load is the highest load on any
 segment in the path and that reliability is the worst
 reliability on any segment in the path.
 
 However, I noticed that Doyle says that load and reliability
 are cummulative.
 
 For reliability, he says: Reliability reflects total outgoing
 error rates of the interfaces along the route.
 
 For load, he says: Load reflects the total outgoing load of the
 interfaces along the route.
 
 
 So, if Doyle is right, I guess we can assume that a router
 accepts a route from a downstream neighbor, looks at
 reliability (expressed as a fraction of 255) in the route,
 looks at the reliability on the incoming interface (also
 expressed as a fraction of 255), and somehow munges those
 together to form a reliability figure that it should pass on to
 its upstream neighbors for that route. Would it multiply the
 values??
 
 Assuming a router actually cares about this part of the
 composite metric, the inverse of this reliabilty result gets
 folded into the metrc. (I say inverse because metric is cost
 and we care about the error rate not the reliability).
 
 
 For load, if Doyle is right, we can assume that a router
 accepts a route from a downstream neighbor, looks at load
 (expressed as a fraction of 255), looks at load for the
 incoming interface (also expressed as a fraction of 255), and
 somehow munges those together to form a load figure that it
 should pass to its upstream neighbors. Does it add them??
 Wouldn't that be adding apples and oranges? 255/255 load on a
 T1 is different from 255/255 load on Fast Ethernet. Of course,
 the router does have the bandwidth for the route too, so it
 could use that for calculating a cummulative load too.
 
 
 So, I think my answer makes life much easier for the routers.
 Just report whichever is worse, the one in the incoming route
 or the one for your incoming interface. The result is that the
 load for a route reflects the highest load of any segment and
 the reliability reflects the worst reliability for any segment.
 It's not quite as granular, but I think it would be fine as a
 metric. I really did think it worked that way, though I can't
 find any documentation that says this. But I think a Cisco
 person told me this.
 
 
 So I tried to do some testing, but of course, load and
 reliability are so variable, and IGRP and EIGRP are so not
 variable, that I didn't have much luck determining the truth.
 Plus I managed to put routes in holddown by increasing the load
 too much!
 
 With IGRP updates only being sent every 90 seconds, they
 obviously don't take into account real-time load and
 reliability anyway. And with EIGRP

IGRP and EIGRP metric [7:66522]

2003-03-30 Thread Priscilla Oppenheimer
Tim Champion  wrote in message 
news:[EMAIL PROTECTED] 
 When calculating the metric of an IGRP route (with non-default 'K' values) 
 which load and reliability values does one use? Do you use the highest, 
 lowest or average value for the entire route? 
 
 Also if anyone could point me to a document on the above it would be 
 appreciated. 
 
 
 Many thanks in advance. 

Remember this oldie but goodie question? Most of the answers were links to
papers that don't answer the question. I answered the question by saying
that load is the highest load on any segment in the path and that
reliability is the worst reliability on any segment in the path.

However, I noticed that Doyle says that load and reliability are cummulative.

For reliability, he says: Reliability reflects total outgoing error rates of
the interfaces along the route.

For load, he says: Load reflects the total outgoing load of the interfaces
along the route.


So, if Doyle is right, I guess we can assume that a router accepts a route
from a downstream neighbor, looks at reliability (expressed as a fraction
of 255) in the route, looks at the reliability on the incoming interface
(also expressed as a fraction of 255), and somehow munges those together to
form a reliability figure that it should pass on to its upstream neighbors
for that route. Would it multiply the values??

Assuming a router actually cares about this part of the composite metric,
the inverse of this reliabilty result gets folded into the metrc. (I say
inverse because metric is cost and we care about the error rate not the
reliability).


For load, if Doyle is right, we can assume that a router accepts a route
from a downstream neighbor, looks at load (expressed as a fraction of 255),
looks at load for the incoming interface (also expressed as a fraction of
255), and somehow munges those together to form a load figure that it should
pass to its upstream neighbors. Does it add them?? Wouldn't that be adding
apples and oranges? 255/255 load on a T1 is different from 255/255 load on
Fast Ethernet. Of course, the router does have the bandwidth for the route
too, so it could use that for calculating a cummulative load too.


So, I think my answer makes life much easier for the routers. Just report
whichever is worse, the one in the incoming route or the one for your
incoming interface. The result is that the load for a route reflects the
highest load of any segment and the reliability reflects the worst
reliability for any segment. It's not quite as granular, but I think it
would be fine as a metric. I really did think it worked that way, though I
can't find any documentation that says this. But I think a Cisco person told
me this.


So I tried to do some testing, but of course, load and reliability are so
variable, and IGRP and EIGRP are so not variable, that I didn't have much
luck determining the truth. Plus I managed to put routes in holddown by
increasing the load too much!

With IGRP updates only being sent every 90 seconds, they obviously don't
take into account real-time load and reliability anyway. And with EIGRP,
there are no updates unless there are changes. So the inclusion of load and
reliability are silly, but I still wonder what they mean if they are used.


If I had enough sniffers I could have tested IGRP. A 90-second update timer
isn't too painful. Even without the metric weights command, the info is
passed in the updates. I would need a couple sniffers to see how the values
change compared to the router interface values.

By the way, even when reliability and load aren't used in the composite, you
can still see their value for a route in the routing table if you do show
ip route . So testing my theory is possible, but not practical in my limited
lab network.


So, has anyone gotten this far in this long-winded message? :-) Does anyone
know how load and reliability are really calculated? Would anyone like to
take on the project to test it? Is it the worst or cummulative?

Please don't send me to a URL that doesn't really answer the question. The
ones that cover the weighting (K values) don't answer the question. The one
that talks about FTP and the question of how often load is calculated also
doesn't answer the question of whether load is cummulative or the worst case
when calculating the metric for a route.

Thanks for listening and thanks in advance for anyone who would like to help
me unravel the mystery!? (Or should we just believe Doyle! That usually
works!)

Priscilla






Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=66522t=66522
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: Unexpected behavior of IGRP and EIGRP [7:64625]

2003-03-10 Thread [EMAIL PROTECTED]
i can't figure out why u r using IGRP in R3, since obviously he would
know about the routes.
Regards, Amar.

I was testing auto-summary with different protocols and I ended up in this
configuration, before remove one of the protocols.

actually it is Eigrp that has a better AD than Igrp, 90 and 100,
respectively, the route u see in ur table has 170 as the AD, therefore
External EIGRP,caused by the implicit redistribution, imposed when using
these routing protocols with the same AS.

If I got that right, even if the value used in the routing table (170) is
higher than the route from IGRP (100), the process will consider the route
better because it is from EIGRP (90).  It makes me wonder how the value 170
is applyed to the route (I know it is not sent by R2, or is it,
indirectly?).





Amar KHELIFI @groupstudy.com em 07/03/2003
21:38:07

Favor responder a Amar KHELIFI 

Enviado Por:  [EMAIL PROTECTED]


Para:  [EMAIL PROTECTED]
cc:

Assunto:Re: Unexpected behavior of IGRP and EIGRP [7:64625]


Hi,
actually it is Eigrp that has a better AD than Igrp, 90 and 100,
respectively, the route u see in ur table has 170 as the AD, therefore
External EIGRP,caused by the implicit redistribution, imposed when using
these routing protocols with the same AS.
so u are having normal behavior of the protocols.
but i can't figure out why u r using IGRP in R3, since obviously he would
know about the routes.
Regards, Amar.

 a icrit dans le message de news:
[EMAIL PROTECTED]
 R1  R2  R3

   router R1 is running igrp process 1
   router R2 is running igrp process 1 and eigrp process 2
   router R3 is running igrp process 1 and eigrp process 2

   R1 is running IGRP on network 10.0.0.0.

   I would expect R1 advertise router 10.0.0.0 to R2 via igrp and R2
   advertise 10.0.0.0 via igrp to R3

   But this is the result of R3 routing table:

   R3#sh ip route


   D192.168.12.0/24 [90/2681856] via 192.168.23.1, 00:04:45,
Serial0.32
3.0.0.0/24 is subnetted, 1 subnets
   C   3.3.3.0 is directly connected, Loopback0
   D EX 10.0.0.0/8 [170/2809856] via 192.168.23.1, 00:04:46, Serial0.32
   C192.168.23.0/24 is directly connected, Serial0.32

   Debug igrp transactions shows R3 receiving news about 10.0.0.0 network,
   but the route is not installed on the routing table via IGRP;  as IGRP
   has a better administrative cost than redistributed routes via EIGRP, I
   would expect the IGRP route to be the routing table.

   R3#debu ip igrp transactions
   IGRP protocol debugging is on
   IP routing:
 IGRP protocol debugging is on

   00:24:24: IGRP: sending update to 255.255.255.255 via Serial0.32
   (192.168.23.2) - suppressing null update
   00:24:56: IGRP: received update from 192.168.23.1 on Serial0.32
   00:24:56:   network 192.168.12.0, metric 10476 (neighbor 8476)
   00:24:56:   network 10.0.0.0, metric 10976 (neighbor 8976)


   R1

   interface Loopback1
ip address 10.10.10.10 255.255.255.0
   !
   interface Serial0.12 point-to-point
ip address 192.168.12.1 255.255.255.0
frame-relay interface-dlci 112
   !
   router igrp 1
network 10.0.0.0
network 192.168.12.0

   R2

   interface Loopback0
ip address 2.2.2.2 255.255.255.0
   !
   interface Serial0.21 point-to-point
ip address 192.168.12.2 255.255.255.0
no ip directed-broadcast
frame-relay interface-dlci 121
   !
   interface Serial0.23 point-to-point
ip address 192.168.23.1 255.255.255.0
no ip directed-broadcast
frame-relay interface-dlci 123
   !
   router eigrp 1
network 192.168.23.0
   !
   router igrp 1
network 192.168.12.0
network 192.168.23.0

   R3

   interface Serial0.32 point-to-point
ip address 192.168.23.2 255.255.255.0
 frame-relay interface-dlci 132
   !
   router eigrp 1
network 192.168.23.0
no eigrp log-neighbor-changes
   !
   router igrp 1
network 192.168.23.0

   Any Thoughts?




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=64925t=64625
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Re: Unexpected behavior of IGRP and EIGRP [7:64625]

2003-03-07 Thread Amar KHELIFI
Hi,
actually it is Eigrp that has a better AD than Igrp, 90 and 100,
respectively, the route u see in ur table has 170 as the AD, therefore
External EIGRP,caused by the implicit redistribution, imposed when using
these routing protocols with the same AS.
so u are having normal behavior of the protocols.
but i can't figure out why u r using IGRP in R3, since obviously he would
know about the routes.
Regards, Amar.

 a icrit dans le message de news:
[EMAIL PROTECTED]
 R1  R2  R3

   router R1 is running igrp process 1
   router R2 is running igrp process 1 and eigrp process 2
   router R3 is running igrp process 1 and eigrp process 2

   R1 is running IGRP on network 10.0.0.0.

   I would expect R1 advertise router 10.0.0.0 to R2 via igrp and R2
   advertise 10.0.0.0 via igrp to R3

   But this is the result of R3 routing table:

   R3#sh ip route


   D192.168.12.0/24 [90/2681856] via 192.168.23.1, 00:04:45, Serial0.32
3.0.0.0/24 is subnetted, 1 subnets
   C   3.3.3.0 is directly connected, Loopback0
   D EX 10.0.0.0/8 [170/2809856] via 192.168.23.1, 00:04:46, Serial0.32
   C192.168.23.0/24 is directly connected, Serial0.32

   Debug igrp transactions shows R3 receiving news about 10.0.0.0 network,
   but the route is not installed on the routing table via IGRP;  as IGRP
   has a better administrative cost than redistributed routes via EIGRP, I
   would expect the IGRP route to be the routing table.

   R3#debu ip igrp transactions
   IGRP protocol debugging is on
   IP routing:
 IGRP protocol debugging is on

   00:24:24: IGRP: sending update to 255.255.255.255 via Serial0.32
   (192.168.23.2) - suppressing null update
   00:24:56: IGRP: received update from 192.168.23.1 on Serial0.32
   00:24:56:   network 192.168.12.0, metric 10476 (neighbor 8476)
   00:24:56:   network 10.0.0.0, metric 10976 (neighbor 8976)


   R1

   interface Loopback1
ip address 10.10.10.10 255.255.255.0
   !
   interface Serial0.12 point-to-point
ip address 192.168.12.1 255.255.255.0
frame-relay interface-dlci 112
   !
   router igrp 1
network 10.0.0.0
network 192.168.12.0

   R2

   interface Loopback0
ip address 2.2.2.2 255.255.255.0
   !
   interface Serial0.21 point-to-point
ip address 192.168.12.2 255.255.255.0
no ip directed-broadcast
frame-relay interface-dlci 121
   !
   interface Serial0.23 point-to-point
ip address 192.168.23.1 255.255.255.0
no ip directed-broadcast
frame-relay interface-dlci 123
   !
   router eigrp 1
network 192.168.23.0
   !
   router igrp 1
network 192.168.12.0
network 192.168.23.0

   R3

   interface Serial0.32 point-to-point
ip address 192.168.23.2 255.255.255.0
 frame-relay interface-dlci 132
   !
   router eigrp 1
network 192.168.23.0
no eigrp log-neighbor-changes
   !
   router igrp 1
network 192.168.23.0

   Any Thoughts?




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=64799t=64625
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


Unexpected behavior of IGRP and EIGRP [7:64625]

2003-03-06 Thread [EMAIL PROTECTED]
R1  R2  R3

  router R1 is running igrp process 1
  router R2 is running igrp process 1 and eigrp process 2
  router R3 is running igrp process 1 and eigrp process 2

  R1 is running IGRP on network 10.0.0.0.

  I would expect R1 advertise router 10.0.0.0 to R2 via igrp and R2
  advertise 10.0.0.0 via igrp to R3

  But this is the result of R3 routing table:

  R3#sh ip route


  D192.168.12.0/24 [90/2681856] via 192.168.23.1, 00:04:45, Serial0.32
   3.0.0.0/24 is subnetted, 1 subnets
  C   3.3.3.0 is directly connected, Loopback0
  D EX 10.0.0.0/8 [170/2809856] via 192.168.23.1, 00:04:46, Serial0.32
  C192.168.23.0/24 is directly connected, Serial0.32

  Debug igrp transactions shows R3 receiving news about 10.0.0.0 network,
  but the route is not installed on the routing table via IGRP;  as IGRP
  has a better administrative cost than redistributed routes via EIGRP, I
  would expect the IGRP route to be the routing table.

  R3#debu ip igrp transactions
  IGRP protocol debugging is on
  IP routing:
IGRP protocol debugging is on

  00:24:24: IGRP: sending update to 255.255.255.255 via Serial0.32
  (192.168.23.2) - suppressing null update
  00:24:56: IGRP: received update from 192.168.23.1 on Serial0.32
  00:24:56:   network 192.168.12.0, metric 10476 (neighbor 8476)
  00:24:56:   network 10.0.0.0, metric 10976 (neighbor 8976)


  R1

  interface Loopback1
   ip address 10.10.10.10 255.255.255.0
  !
  interface Serial0.12 point-to-point
   ip address 192.168.12.1 255.255.255.0
   frame-relay interface-dlci 112
  !
  router igrp 1
   network 10.0.0.0
   network 192.168.12.0

  R2

  interface Loopback0
   ip address 2.2.2.2 255.255.255.0
  !
  interface Serial0.21 point-to-point
   ip address 192.168.12.2 255.255.255.0
   no ip directed-broadcast
   frame-relay interface-dlci 121
  !
  interface Serial0.23 point-to-point
   ip address 192.168.23.1 255.255.255.0
   no ip directed-broadcast
   frame-relay interface-dlci 123
  !
  router eigrp 1
   network 192.168.23.0
  !
  router igrp 1
   network 192.168.12.0
   network 192.168.23.0

  R3

  interface Serial0.32 point-to-point
   ip address 192.168.23.2 255.255.255.0
frame-relay interface-dlci 132
  !
  router eigrp 1
   network 192.168.23.0
   no eigrp log-neighbor-changes
  !
  router igrp 1
   network 192.168.23.0

  Any Thoughts?




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=64625t=64625
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]


IGRP to EIGRP redistribute problem (VLSM to FLSM) [7:43222]

2002-05-03 Thread Tey Haw Ching

HI all,
 Need some advise on the following IGRP to Eigrp route distribute
problem.
 Problem: 137.33.0.0 is possible down after a while at both r5 and
r6.
 End result to achieve: r6 can ping r5 loopback0 or r5 to r6.

 Both R5 and R6 have a loopback ip address(137.33.5.5/32 and
137.33.6.6/32) which using Host subnet. The problem seem to be FLSM to
VLSM route distribute and I have try all the possible way(e.g. summary,
policy route, distribute-list and tunnel) but still have not idea how to
resolve the above problem.
R6 is running both IGRP and EIGRP.
Below is the configuration.
R5
-
host r5
interface Loopback0
 ip address 137.33.5.5 255.255.255.0
!
interface Ethernet0
 no ip address
 no keepalive
!
interface Serial0
 no ip address
 no keepalive
 shutdown
 no fair-queue
 clockrate 64000
!
interface Serial1
 bandwidth 64000
 backup delay 3 3
 backup interface BRI0
 ip address 134.1.56.5 255.255.255.0
 clockrate 64000
!
interface Serial2
 no ip address
 shutdown
!
interface Serial3
 no ip address
 shutdown
!
interface BRI0
 description ISDN No 7952 1478
 bandwidth 64000
 ip address 134.1.35.5 255.255.255.0
 encapsulation ppp
 dialer map ip 134.1.35.3 name r3 79529389
 dialer load-threshold 192 outbound
 dialer watch-group 1
 dialer-group 1
 isdn switch-type basic-net3
 ppp authentication chap callin
 ppp multilink
!
router igrp 10
 timers basic 5 5 5 5
 redistribute connected
 network 134.1.0.0
 network 137.33.0.0
 metric weights 0 1 1 1 0 0
!
ip local policy route-map pol1
ip kerberos source-interface any
ip classless
no ip http server
!
access-list 1 permit 137.24.0.0
access-list 1 permit 137.33.6.6
access-list 1 permit 137.33.2.2
access-list 1 permit 137.33.1.1
access-list 1 permit 137.33.3.3
access-list 1 permit 137.33.4.4
dialer-list 1 protocol ip permit
route-map loopback permit 10
 match interface Loopback0
!
route-map pol1 permit 10
 match ip route-source 1
 set interface Serial1
!
route-map pol1 permit 20

r5#sir
Codes: C - connected, S - static, I - IGRP, 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, E - EGP
   i - IS-IS, 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 not set

I202.6.6.0/24 [100/2656] via 134.1.56.6, 00:00:03, Serial1
 137.33.0.0/24 is subnetted, 1 subnets
C   137.33.5.0 is directly connected, Loopback0
I202.2.2.0/24 [100/2656] via 134.1.56.6, 00:00:03, Serial1
 134.1.0.0/24 is subnetted, 1 subnets
C   134.1.56.0 is directly connected, Serial1

hostname r6
!
logging rate-limit console 10 except errors
!
ip subnet-zero
no ip finger
no ip domain-lookup
!
cns event-service server
!
!
!
dlsw local-peer peer-id 134.1.6.6
dlsw remote-peer 0 frame-relay interface Serial0 604 pass-thru
!
!
interface Loopback0
 ip address 137.33.6.6 255.255.255.0
!
interface Loopback1
 ip address 202.6.6.6 255.255.255.0
!
interface Loopback2
 description ATM Emulation interface
 ip address 202.2.2.2 255.255.255.0
!
interface Ethernet0
 ip address 150.100.6.6 255.255.255.0
!
interface Serial0
 ip address 134.1.34.6 255.255.255.0
 encapsulation frame-relay
 ip ospf message-digest-key 1 md5 hackme
 ip ospf network point-to-multipoint
 shutdown
 no fair-queue
 clockrate 64000
 frame-relay map dlsw 604 broadcast
 frame-relay map ip 134.1.34.3 604 broadcast
 frame-relay map ip 134.1.34.4 604 broadcast
 no frame-relay inverse-arp
!
interface Serial1
 ip address 134.1.26.6 255.255.255.0
 ip policy route-map pol1
 shutdown
 clockrate 64000
!
interface Serial2
 ip address 134.1.56.6 255.255.255.0
!
interface Serial3
 no ip address
 shutdown
!
interface BRI0
 no ip address
 shutdown
!
router eigrp 100
 redistribute igrp 10 metric 1000 100 255 1 1500
 network 134.1.26.0 0.0.0.255
 no auto-summary
 no eigrp log-neighbor-changes
!
router ospf 1
 log-adjacency-changes
 area 1 authentication message-digest
 passive-interface Loopback0
 passive-interface Loopback1
 passive-interface Loopback2
 passive-interface Serial1
 passive-interface Serial2
 network 134.1.34.0 0.0.0.255 area 1
 network 150.100.6.0 0.0.0.255 area 1
 default-metric 50
!
router igrp 10
 timers basic 5 5 5 5
 redistribute eigrp 100 metric 1000 100 255 1 1500
 passive-interface Loopback0
 passive-interface Serial0
 passive-interface Serial1
 network 134.1.0.0
 network 137.33.0.0
 network 202.2.2.0
 network 202.6.6.0
!
ip kerberos source-interface any
ip classless
no ip http server
!
access-list 1 permit 137.33.5.5
access-list 2 deny   137.33.0.0 0.0.255.255
access-list 2 permit any
access-list 3 permit 134.1.13.0 0.0.0.255
access-list 3 permit 150.100.0.0 0.0.255.255
route-map pol1 permit 10
 match ip address 1
 set interface Serial2
!
route-map pol1 permit 20
!
!
alias

RE: IGRP to EIGRP redistribute problem (VLSM to FLSM) [7:43222]

2002-05-03 Thread Ladrach, Daniel E.

If an IGRP process and an EIGRP process have the same process IDs, they will
redistribute automatically. Change your router eigrp 100 to router eigrp 10.
Doyle Volume 1 has some good information in it.

Daniel Ladrach
CCNA, CCNP
WorldCom


 -Original Message-
 From: Tey Haw Ching [mailto:[EMAIL PROTECTED]]
 Sent: Friday, May 03, 2002 9:53 AM
 To: [EMAIL PROTECTED]
 Subject: IGRP to EIGRP redistribute problem (VLSM to FLSM) [7:43222]
 
 
 HI all,
  Need some advise on the following IGRP to Eigrp route distribute
 problem.
  Problem: 137.33.0.0 is possible down after a while at both r5 and
 r6.
  End result to achieve: r6 can ping r5 loopback0 or r5 to r6.
 
  Both R5 and R6 have a loopback ip address(137.33.5.5/32 and
 137.33.6.6/32) which using Host subnet. The problem seem to be FLSM to
 VLSM route distribute and I have try all the possible 
 way(e.g. summary,
 policy route, distribute-list and tunnel) but still have not 
 idea how to
 resolve the above problem.
 R6 is running both IGRP and EIGRP.
 Below is the configuration.
 R5
 -
 host r5
 interface Loopback0
  ip address 137.33.5.5 255.255.255.0
 !
 interface Ethernet0
  no ip address
  no keepalive
 !
 interface Serial0
  no ip address
  no keepalive
  shutdown
  no fair-queue
  clockrate 64000
 !
 interface Serial1
  bandwidth 64000
  backup delay 3 3
  backup interface BRI0
  ip address 134.1.56.5 255.255.255.0
  clockrate 64000
 !
 interface Serial2
  no ip address
  shutdown
 !
 interface Serial3
  no ip address
  shutdown
 !
 interface BRI0
  description ISDN No 7952 1478
  bandwidth 64000
  ip address 134.1.35.5 255.255.255.0
  encapsulation ppp
  dialer map ip 134.1.35.3 name r3 79529389
  dialer load-threshold 192 outbound
  dialer watch-group 1
  dialer-group 1
  isdn switch-type basic-net3
  ppp authentication chap callin
  ppp multilink
 !
 router igrp 10
  timers basic 5 5 5 5
  redistribute connected
  network 134.1.0.0
  network 137.33.0.0
  metric weights 0 1 1 1 0 0
 !
 ip local policy route-map pol1
 ip kerberos source-interface any
 ip classless
 no ip http server
 !
 access-list 1 permit 137.24.0.0
 access-list 1 permit 137.33.6.6
 access-list 1 permit 137.33.2.2
 access-list 1 permit 137.33.1.1
 access-list 1 permit 137.33.3.3
 access-list 1 permit 137.33.4.4
 dialer-list 1 protocol ip permit
 route-map loopback permit 10
  match interface Loopback0
 !
 route-map pol1 permit 10
  match ip route-source 1
  set interface Serial1
 !
 route-map pol1 permit 20
 
 r5#sir
 Codes: C - connected, S - static, I - IGRP, 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, E - EGP
i - IS-IS, 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 not set
 
 I202.6.6.0/24 [100/2656] via 134.1.56.6, 00:00:03, Serial1
  137.33.0.0/24 is subnetted, 1 subnets
 C   137.33.5.0 is directly connected, Loopback0
 I202.2.2.0/24 [100/2656] via 134.1.56.6, 00:00:03, Serial1
  134.1.0.0/24 is subnetted, 1 subnets
 C   134.1.56.0 is directly connected, Serial1
 
 hostname r6
 !
 logging rate-limit console 10 except errors
 !
 ip subnet-zero
 no ip finger
 no ip domain-lookup
 !
 cns event-service server
 !
 !
 !
 dlsw local-peer peer-id 134.1.6.6
 dlsw remote-peer 0 frame-relay interface Serial0 604 pass-thru
 !
 !
 interface Loopback0
  ip address 137.33.6.6 255.255.255.0
 !
 interface Loopback1
  ip address 202.6.6.6 255.255.255.0
 !
 interface Loopback2
  description ATM Emulation interface
  ip address 202.2.2.2 255.255.255.0
 !
 interface Ethernet0
  ip address 150.100.6.6 255.255.255.0
 !
 interface Serial0
  ip address 134.1.34.6 255.255.255.0
  encapsulation frame-relay
  ip ospf message-digest-key 1 md5 hackme
  ip ospf network point-to-multipoint
  shutdown
  no fair-queue
  clockrate 64000
  frame-relay map dlsw 604 broadcast
  frame-relay map ip 134.1.34.3 604 broadcast
  frame-relay map ip 134.1.34.4 604 broadcast
  no frame-relay inverse-arp
 !
 interface Serial1
  ip address 134.1.26.6 255.255.255.0
  ip policy route-map pol1
  shutdown
  clockrate 64000
 !
 interface Serial2
  ip address 134.1.56.6 255.255.255.0
 !
 interface Serial3
  no ip address
  shutdown
 !
 interface BRI0
  no ip address
  shutdown
 !
 router eigrp 100
  redistribute igrp 10 metric 1000 100 255 1 1500
  network 134.1.26.0 0.0.0.255
  no auto-summary
  no eigrp log-neighbor-changes
 !
 router ospf 1
  log-adjacency-changes
  area 1 authentication message-digest
  passive-interface Loopback0
  passive-interface Loopback1
  passive-interface Loopback2
  passive-interface Serial1
  passive-interface Serial2
  network 134.1.34.0 0.0.0.255 area 1
  network 150.100.6.0 0.0.0.255

IGRP over EIGRP...How?? [7:33760]

2002-01-30 Thread Cisco Nuts

Hello,
I have 3  routers  running  both  Eigrp 1 and Igrp  100.  I  configed. a  
distance  of 4 for Igrp so that it  would  be the  preferred  protocol  but 
the  routing  table shows both Eigrp and Igrp learned route for the same 
netw.  I am  trying to understand why?  I expected to only see Igrp learned 
routes since the lower admin  dist.  of 4 would take over  Eigrp's  dist.  
of 90...but it is not apparently so.  Any ideas?  Thank you.
Example
on RTC:
6.0.0.0/8  is  variably  subnetted,  2  subnets,  2 masks
D  6.6.6.6/32 [90/4064] via 192.168.10.241,  00:00:05, Serial0
I  6.0.0.0/8  [4/158750] via 192.168.10.241, 00:00:05, Serial

Config.  on RTC:   !
router eigrp 1
passive-interface  Ethernet0
network 7.0.0.0
network 192.168.10.0
no auto-summary
!
router igrp 100
passive-interface  Ethernet0
network 7.0.0.0
network 192.168.10.0
distance 4
!

_
Chat with friends online, try MSN Messenger: http://messenger.msn.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=33760t=33760
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



RE: IGRP over EIGRP...How?? [7:33760]

2002-01-30 Thread Mike Bernico

Longest match wins over admin distance.  admin distance only breaks a tie
between two routes of equal length.

Mike

---
Mike Bernico [EMAIL PROTECTED]
Illinois Century Network  http://www.illinois.net
(217) 557-6555


 -Original Message-
 From: Cisco Nuts [mailto:[EMAIL PROTECTED]]
 Sent: Wednesday, January 30, 2002 3:02 PM
 To: [EMAIL PROTECTED]
 Subject: IGRP over EIGRP...How?? [7:33760]
 
 
 Hello,
 I have 3  routers  running  both  Eigrp 1 and Igrp  100.  I  
 configed. a  
 distance  of 4 for Igrp so that it  would  be the  preferred  
 protocol  but 
 the  routing  table shows both Eigrp and Igrp learned route 
 for the same 
 netw.  I am  trying to understand why?  I expected to only 
 see Igrp learned 
 routes since the lower admin  dist.  of 4 would take over  
 Eigrp's  dist.  
 of 90...but it is not apparently so.  Any ideas?  Thank you.
   
   Example
 on RTC:
 6.0.0.0/8  is  variably  subnetted,  2  subnets,  2 masks
 D  6.6.6.6/32 [90/4064] via 192.168.10.241,  00:00:05, Serial0
 I  6.0.0.0/8  [4/158750] via 192.168.10.241, 00:00:05, Serial
 
 Config.  on RTC: !
 router eigrp 1
 passive-interface  Ethernet0
 network 7.0.0.0
 network 192.168.10.0
 no auto-summary
 !
 router igrp 100
 passive-interface  Ethernet0
 network 7.0.0.0
 network 192.168.10.0
 distance 4
 !
 
 _
 Chat with friends online, try MSN Messenger: http://messenger.msn.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=33768t=33760
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: IGRP over EIGRP...How?? [7:33760]

2002-01-30 Thread JEK

Mike/cisconuts

That's true on the longest match wins, but that's not the exact issue here.
The problem is
that IGRP is classful and EIGRP is classless.  So essentially IGRP will
install the classful
route of 6/8 and EIGRP will install the route of 6.6.6.6/32 into the routing
table.  Cheers,

- jek


Mike Bernico  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
 Longest match wins over admin distance.  admin distance only breaks a tie
 between two routes of equal length.

 Mike

 ---
 Mike Bernico [EMAIL PROTECTED]
 Illinois Century Network  http://www.illinois.net
 (217) 557-6555


  -Original Message-
  From: Cisco Nuts [mailto:[EMAIL PROTECTED]]
  Sent: Wednesday, January 30, 2002 3:02 PM
  To: [EMAIL PROTECTED]
  Subject: IGRP over EIGRP...How?? [7:33760]
 
 
  Hello,
  I have 3  routers  running  both  Eigrp 1 and Igrp  100.  I
  configed. a
  distance  of 4 for Igrp so that it  would  be the  preferred
  protocol  but
  the  routing  table shows both Eigrp and Igrp learned route
  for the same
  netw.  I am  trying to understand why?  I expected to only
  see Igrp learned
  routes since the lower admin  dist.  of 4 would take over
  Eigrp's  dist.
  of 90...but it is not apparently so.  Any ideas?  Thank you.
 
  Example
  on RTC:
  6.0.0.0/8  is  variably  subnetted,  2  subnets,  2 masks
  D  6.6.6.6/32 [90/4064] via 192.168.10.241,  00:00:05, Serial0
  I  6.0.0.0/8  [4/158750] via 192.168.10.241, 00:00:05, Serial
 
  Config.  on RTC:!
  router eigrp 1
  passive-interface  Ethernet0
  network 7.0.0.0
  network 192.168.10.0
  no auto-summary
  !
  router igrp 100
  passive-interface  Ethernet0
  network 7.0.0.0
  network 192.168.10.0
  distance 4
  !
 
  _
  Chat with friends online, try MSN Messenger: http://messenger.msn.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=33787t=33760
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Variance in IGRP and EIGRP [7:9754]

2001-06-25 Thread Lupi, Guy

I am working with a lab setup and have a question on variance.  I know what
the variance does, but it does not work with all routes.  I have the
variance set to the maximum on all routers (128), but only certain unequal
routes get placed in the routing table.  If I shut down the link on one of
the routers the higher metric routes get installed, but only in the event of
a link failure.  I know there are some rules that govern the installation of
a route once the variance is configured, if someone has a concise
explanation of what they are and how they work it would be greatly
appreciated.  Thanks in advance.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=9754t=9754
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Variance in IGRP and EIGRP [7:9756]

2001-06-25 Thread Lupi, Guy

Please disregard my earlier question, I found the answer.  Apparently for a
route to be installed for unequal cost load balancing the routes metric must
still be lower that the routers feasible distance to the destination, and
that is why I am only seeing the routes in the event of a link failure.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=9756t=9756
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Variance in IGRP and EIGRP [7:9754]

2001-06-25 Thread Ednilson Rosa

From BSCN Guide:

Only paths that are feasible can be used for the load balance and included
in the routing table. Feasible conditions are:

1) Local best metric  Best metric learned from the next router.

2) The multiplier x Local best metric for the destination  Metric through
the next router.

If both conditions are met, the route is called feasible and can be added to
the routing table.

Hope this helps!

ER
CCNA

- Original Message -
From: Lupi, Guy 
To: 
Sent: Monday, June 25, 2001 8:39 AM
Subject: Variance in IGRP and EIGRP [7:9754]


I am working with a lab setup and have a question on variance.  I know what
the variance does, but it does not work with all routes.  I have the
variance set to the maximum on all routers (128), but only certain unequal
routes get placed in the routing table.  If I shut down the link on one of
the routers the higher metric routes get installed, but only in the event of
a link failure.  I know there are some rules that govern the installation of
a route once the variance is configured, if someone has a concise
explanation of what they are and how they work it would be greatly
appreciated.  Thanks in advance.




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=9760t=9754
--
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: IGRP to EIGRP conversion #2

2001-02-19 Thread Robert Padjen

router eigrp 1
  distance eigrp (internal) (external)


--- suaveguru [EMAIL PROTECTED] wrote:
 sorry mind if I ask what is the command to change
 default admin dist of a routing protocol
 
 regards,
 suaveguru
 --- Russell Lusignan [EMAIL PROTECTED] wrote:
  Enable EIGRP on the routers and add the network
  statements as you normally
  would..  raise the administrative distance of
 EIGRP
  to 110, I believe IGRP
  is 100 so even though both routing protocols are
  running on every router,
  EIGRP routes will be rejected because IGRP has a
  lower admin distance..
  Once the routers are ready, simply put the admin
  distance of EIGRP back to
  90 and it should converge within a few mins.. 
 Once
  the network is using
  only EIGRP learned routes, remote IGRP off the
  routers.
  
  hope that helps
  Russ..
  
  
  ""Roberts, Timothy"" [EMAIL PROTECTED]
  wrote in message
 

[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
  
   I have a hub site with 5 remote sites connecting
  to it via frame relay.
   They are all running IGRP with the same AS. 
 What
  would be the best way to
   migrate from IGRP to EIGRP?  Starting by
 enabling
  EIGRP on the core router
   and run both IGRP and EIGRP.  Then convert the
  spokes one by one.  Then
   remove IGRP from the core.  Can I just enable
  EIGRP on the remotes, allow
   some time to propagate routes in to the table,
 and
  then disable IGRP?  The
   people up stairs will not allow for any
  significant down time.
   Thanks
  
   _
   FAQ, list archives, and subscription info:
  http://www.groupstudy.com/list/cisco.html
   Report misconduct and Nondisclosure violations
 to
  [EMAIL PROTECTED]
  
  
  
  _
  FAQ, list archives, and subscription info:
  http://www.groupstudy.com/list/cisco.html
  Report misconduct and Nondisclosure violations to
 [EMAIL PROTECTED]
 
 
 __
 Do You Yahoo!?
 Get personalized email addresses from Yahoo! Mail -
 only $35 
 a year!  http://personal.mail.yahoo.com/
 
 _
 FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]


=
Robert Padjen

__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: IGRP to EIGRP conversion #2

2001-02-17 Thread suaveguru

sorry mind if I ask what is the command to change
default admin dist of a routing protocol

regards,
suaveguru
--- Russell Lusignan [EMAIL PROTECTED] wrote:
 Enable EIGRP on the routers and add the network
 statements as you normally
 would..  raise the administrative distance of EIGRP
 to 110, I believe IGRP
 is 100 so even though both routing protocols are
 running on every router,
 EIGRP routes will be rejected because IGRP has a
 lower admin distance..
 Once the routers are ready, simply put the admin
 distance of EIGRP back to
 90 and it should converge within a few mins..  Once
 the network is using
 only EIGRP learned routes, remote IGRP off the
 routers.
 
 hope that helps
 Russ..
 
 
 ""Roberts, Timothy"" [EMAIL PROTECTED]
 wrote in message

[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
 
  I have a hub site with 5 remote sites connecting
 to it via frame relay.
  They are all running IGRP with the same AS.  What
 would be the best way to
  migrate from IGRP to EIGRP?  Starting by enabling
 EIGRP on the core router
  and run both IGRP and EIGRP.  Then convert the
 spokes one by one.  Then
  remove IGRP from the core.  Can I just enable
 EIGRP on the remotes, allow
  some time to propagate routes in to the table, and
 then disable IGRP?  The
  people up stairs will not allow for any
 significant down time.
  Thanks
 
  _
  FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
  Report misconduct and Nondisclosure violations to
 [EMAIL PROTECTED]
 
 
 
 _
 FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]


__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: IGRP to EIGRP conversion #2

2001-02-16 Thread Robert Padjen

Timothy -

I think that you've asked this a few times but never
with this type of information. Let's get things a bit
more organized with all due respect. I really would
like to help you as migrations to EIGRP can be tricky.

First, what are the models and memory installations of
the routers? Second, what are the remote links and
their utilizations? Third, are the remotes all stubs -
just an Ethernet on the other side? Is the frame-relay
configuration point to point or multipoint?

I ask because EIGRP usually does not do well in
hub-and-spoke designs. This is due to the number of
neighbor relationships that are established. With five
neighbors and solid routers you might be fine, but
growth would be a concern. Since you are running F/R
you might want to consider ODR, which would take no
additional bandwidth. You might also want to look at
RIP v2. EIGRP is really good for larger, more complex
networks. Its usually overkill for smaller hub/spokes,
which usually are in processor/memory challenged
networks.

I look forward to hearing from you.


--- "Roberts, Timothy" [EMAIL PROTECTED]
wrote:
 
 I have a hub site with 5 remote sites connecting to
 it via frame relay.
 They are all running IGRP with the same AS.  What
 would be the best way to
 migrate from IGRP to EIGRP?  Starting by enabling
 EIGRP on the core router
 and run both IGRP and EIGRP.  Then convert the
 spokes one by one.  Then
 remove IGRP from the core.  Can I just enable EIGRP
 on the remotes, allow
 some time to propagate routes in to the table, and
 then disable IGRP?  The
 people up stairs will not allow for any significant
 down time.  
 Thanks
 
 _
 FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]


=
Robert Padjen

__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Converting from IGRP to EIGRP

2001-02-16 Thread Robert Padjen

Cisco provides a feature called automatic
redistribution (or something like that). If you make
the process ID/AS number for EIGRP the same as IGRP on
the router it will automatically redistribute in both
directions.

This is a bad idea for all but the simplest networks.
In the best redistributions a designer wants to
prevent a route from coming back and looping (AD and
metric should normally prevent this, but it helps to
know your network). Also, summarization and manual
control of the routes is prefered for EIGRP under most
circumstances. Lastly, why lose control over somehting
that is so simple - automatation indicates that the
administrator does not understand the requirements,
which would usually complicate troubleshooting. 


--- Santosh Koshy [EMAIL PROTECTED] wrote:
  First, please do not put everything in the same
 AS.
  This is a very bad thing, and I really wish Cisco
  would kill the feature. (I think it was placed in
  there for marketing)
 
 I dont get this robert Please explain the
 above...
 
 
 
 
 _
 FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]


=
Robert Padjen

__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



IGRP to EIGRP conversion #2

2001-02-15 Thread Roberts, Timothy


I have a hub site with 5 remote sites connecting to it via frame relay.
They are all running IGRP with the same AS.  What would be the best way to
migrate from IGRP to EIGRP?  Starting by enabling EIGRP on the core router
and run both IGRP and EIGRP.  Then convert the spokes one by one.  Then
remove IGRP from the core.  Can I just enable EIGRP on the remotes, allow
some time to propagate routes in to the table, and then disable IGRP?  The
people up stairs will not allow for any significant down time.  
Thanks

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Converting from IGRP to EIGRP

2001-02-14 Thread Roberts, Timothy


I posted this a few weeks ago and only got a few responses so I thought that
I would try again.  What would be the best way to migrate from IGRP to
EIGRP?  Everything is in the same AS.  Should I just add the EIGRP
statements to all of the routers and let EIRE do the redistribution
automatically?  Any ideas would be appreciated.
Thanks

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Converting from IGRP to EIGRP

2001-02-14 Thread Robert Padjen

First, please do not put everything in the same AS.
This is a very bad thing, and I really wish Cisco
would kill the feature. (I think it was placed in
there for marketing)

There are two standard ways to do this. The first is
border - you simply redistribute and filter with
distribute lists. The redistribution point can be
moved as you convert, or more added (although you
should only have two routers invloved if possible).

The other is overlay. Both IGRP and EIGRP run on all
routers in the network, but EIGRP's AD is weighted
higher. Then you pull IGRP off. Any router that is not
running IGRP will advertise the routes via EIGRP, and
the only real trick is memory and making sure that you
work from the outside in on the IGRP removal.


--- "Roberts, Timothy" [EMAIL PROTECTED]
wrote:
 
 I posted this a few weeks ago and only got a few
 responses so I thought that
 I would try again.  What would be the best way to
 migrate from IGRP to
 EIGRP?  Everything is in the same AS.  Should I just
 add the EIGRP
 statements to all of the routers and let EIRE do the
 redistribution
 automatically?  Any ideas would be appreciated.
 Thanks
 
 _
 FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]


=
Robert Padjen

__
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Converting from IGRP to EIGRP

2001-02-14 Thread Santosh Koshy

 First, please do not put everything in the same AS.
 This is a very bad thing, and I really wish Cisco
 would kill the feature. (I think it was placed in
 there for marketing)

I dont get this robert Please explain the above...




_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: Converting from IGRP to EIGRP

2001-02-14 Thread Grep

Having just recently done a migration from IGRP to EIGRP in a hub and spoke
network, I learned a few basic guidelines for the migration.

#1.  Have a plan!  I cannot tell you how many times I came across engineers
just wanting to just flip the switch and enable EIGRP without any
pre-planning.  It is imperative that one understands the need for good
subnetting and summarization.  Also, it is critical, that in the event of a
failure during the migration plan, you also have a back out plan.

#2.  Do one location at a time.  When you make a change, minimize variables.
Now, this step can be open for argument and it truly depends on your network
topology and your plan.  The reason I bring it up is because it proved
useful in my hub and spoke network migration.  What I did for each location
was to run IGRP and EIGRP with the same process number on the hub.  When I
migrated a site, I enabled EIGRP, and verified the EIGRP routes were
propagating.  Once verified, I disabled IGRP on the remote router and on the
hub side, under IGRP, I specified a passive interface for that
point-to-point sub-interface.  It works well in my case because if a problem
arose, I could pin it down to one or the other routing protocol.

#3.   After making changes, monitor for a decent period of time to determine
if everything went smoothly.  For my changes, I picked 3 days.  I had
international sites, so I needed to see data patterns across time zones.

#4.  Document the hell out of what you did.

#5.  Bonus!  In my research, I also discovered that in the newer versions of
IOS, there is such thing as a "stub" network in terms of EIGRP.  It allows
for maximum stability in a hub and spoke network.  There is a great page on
CCO that describes it well:

 http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/12
0limit/120s/120s15/eigrpstb.htm#16026

watch the line wrap

Anyway, I hope my own experience can add to yours!

-Joseph

--
From: "Santosh Koshy" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Newsgroups: groupstudy.cisco
Subject: Re: Converting from IGRP to EIGRP
Date: Wed, Feb 14, 2001, 5:42 PM


 First, please do not put everything in the same AS.
 This is a very bad thing, and I really wish Cisco
 would kill the feature. (I think it was placed in
 there for marketing)

 I dont get this robert Please explain the above...




 _
 FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



IGRP to EIGRP

2001-01-31 Thread Roberts, Timothy


I am looking for some suggestions on what would be the easiest way to
convert from IGRP to EIGRP in a large scale environment?
Thanks

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: IGRP to EIGRP

2001-01-31 Thread Jason Fletcher

Check this out:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/np1_c
/1cprt1/1ceigrp.htm#xtocid84274

Jason

""Roberts, Timothy"" [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...

 I am looking for some suggestions on what would be the easiest way to
 convert from IGRP to EIGRP in a large scale environment?
 Thanks

 _
 FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]



Re: IGRP to EIGRP

2001-01-31 Thread Robert Padjen

You have two choices for all intents and purposes. The
first is divide and attack. Pick a redistribution
point and move that point through the migration. This
is a great method if you are building new services at
the same time.

The second is overlay. We are doing this now, and it
works, but its a bit more complex to backout and
manage during migration. Effectively you place EIGRP
on all routers with a higher AD. IGRP is the protocol
in use due to the AD. Usually EIGRP will have
summaries which will not be used but will be in the
table. When ready start pulling IGRP off the routers -
everything is running EIGRP, so the routes will be
there.

Don't ever use the 'automatic' redistribution that
Cisco provides, always use 'no auto-summary' and take
a look at Pepelnjak's book.

Good luck.
--- "Roberts, Timothy" [EMAIL PROTECTED]
wrote:
 
 I am looking for some suggestions on what would be
 the easiest way to
 convert from IGRP to EIGRP in a large scale
 environment?
 Thanks
 
 _
 FAQ, list archives, and subscription info:
 http://www.groupstudy.com/list/cisco.html
 Report misconduct and Nondisclosure violations to
[EMAIL PROTECTED]


=
Robert Padjen

__
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

_
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]