From: Joe Soricelli (jsoricelli@xxxxxxxx)
Date: Fri Oct 15 1999 - 00:28:27 GMT-3
The IPX route table wasn't attached, but my SWAG is that the route A is 3
ticks. Following along that path, it might be that even though some of the
interfaces are serial (DS3), the bandwidth is high enough that IPX is seeing
it as a LAN-like interface and is therefore giving it 1 tick and not 6. So,
the 3 high speed hops via route A is 3 ticks vice the 1 T1 hop is 6 ticks.
Route A is now more preferable.
-joe
------------------------------------------------------------------
Joseph M. Soricelli, CCIE #4803, CCNP, CCSI #20666
EMAIL: jsoricelli@ccci.com
Chesapeake Network Solutions
8110 Gatehouse Road, Suite 101E Phone: (703) 207-0757
Falls Church, VA 22042 Fax: (703) 207-0441
FYI - About Chesapeake: We are a Cisco Certified Training and
professional services partner. We offer most of the Cisco
training courses as well as training for Fore, NetScout, and
CheckPoint-1 Firewalls. We provide network consulting services,
including design, network health, management, firewall,
and problem solving. We now have 23 CCIEs on our staff
of instructor/consultants.
-------------------------------------------------------------------
-----Original Message-----
From: jaarons-hotmail <jaarons@hotmail.com>
To: Joe Soricelli <jsoricelli@fridge.ccci.com>
Cc: ccielab@groupstudy.com <ccielab@groupstudy.com>
Date: Thursday, October 14, 1999 8:52 PM
Subject: Re: EIGRP route calculation
>Here were the results. Route A was indeed a much better metric (69854) vs
>Route B (2181634). What I don't understand is why IPX RIP is following
>Choice A. It should be using Ticks and there would be more ticks via Route
>A, making Route B the perfered route with fewer Ticks. Can you explain why
>?
>
>Router1#show ip route 168.175.46.0
>Routing entry for x.y.z.a/24
> Known via "eigrp 220", distance 110, metric 69854, type internal
> Redistributing via eigrp 120
> Last update from x.y.z.a on Serial5/0, 00:00:43 ago
> Routing Descriptor Blocks:
> * x.y.z.a, from x.y.z.a, 00:00:43 ago, via Serial5/0
> Route metric is 69854, traffic share count is 1
> Total delay is 500 microseconds, minimum bandwidth is 45045 Kbit
> Reliability 251/255, minimum MTU 1500 bytes
> Loading 1/255, Hops 3
>
>funds-wfrch-va3#show ipx route
>
>----- Original Message -----
>From: Joe Soricelli <jsoricelli@ccci.com>
>To: <ccielab@groupstudy.com>
>Sent: Thursday, October 14, 1999 2:57 PM
>Subject: Re: EIGRP route calculation
>
>
>> The maps helped out, Thanks.
>>
>> I can tell you that unless the defaults have been altered, that Choice A
>> will give a better metric due to bandwidth speeds.
>>
>> When you actually do the calculation based on the show int stats below,
>you
>> get 68352 for Choice A and 2178048 for Choice B. Not even close!!
>>
>> -joe
>> ------------------------------------------------------------------
>> Joseph M. Soricelli, CCIE #4803, CCNP, CCSI #20666
>> EMAIL: jsoricelli@ccci.com
>>
>> Chesapeake Network Solutions
>> 8110 Gatehouse Road, Suite 101E Phone: (703) 207-0757
>> Falls Church, VA 22042 Fax: (703) 207-0441
>>
>> FYI - About Chesapeake: We are a Cisco Certified Training and
>> professional services partner. We offer most of the Cisco
>> training courses as well as training for Fore, NetScout, and
>> CheckPoint-1 Firewalls. We provide network consulting services,
>> including design, network health, management, firewall,
>> and problem solving. We now have 23 CCIEs on our staff
>> of instructor/consultants.
>> -------------------------------------------------------------------
>>
>> -----Original Message-----
>> From: Jason Aarons <jaarons@hotmail.com>
>> To: jsoricelli@fridge.ccci.com <jsoricelli@fridge.ccci.com>;
>> ccielab@groupstudy.com <ccielab@groupstudy.com>
>> Date: Thursday, October 14, 1999 2:27 PM
>> Subject: Re: EIGRP route calculation
>>
>>
>> >Here is a map of the choices. Choice A has not been installed (yet) but
>> >neeed to know if it will create a better EIGRP metric than Choice B.
>Also,
>> >this is good stuff..since I included load with EIGRP into the picture..
>> >
>> >
>> >Choice A.
>>
>>Source---FE---Router1--DS3--Router2--FE---Router3---OC12---Router4---FE---
-
>> Destination
>> >
>> >Choice B.
>> >Source----FE---Router1----T1----Router4----FE----Desination
>> >
>> >
>> >After mapping it out, I added some details below and corrected some
>> errors -
>> >jason
>> >
>> >
>> >----Original Message Follows----
>> >From: "Joe Soricelli" <jsoricelli@ccci.com>
>> >To: "Jason Aarons" <jaarons@hotmail.com>
>> >Subject: Re: EIGRP route calculation
>> >Date: Thu, 14 Oct 1999 08:33:56 -0400
>> >
>> >Jason-
>> >
>> >A little more detail please. First, a map would be good. Second, are
>you
>> >trying to figure out why one route was choosen over another?
>> >
>> >-joe
>> >------------------------------------------------------------------
>> >
>> >-----Original Message-----
>> >From: Jason Aarons <jaarons@hotmail.com>
>> >To: ccielab@groupstudy.com <ccielab@groupstudy.com>
>> >Date: Wednesday, October 13, 1999 5:47 PM
>> >Subject: EIGRP route calculation
>> >
>> >
>> > >Problem:
>> > >
>> > >Using K1, K2, K3 (bandwidth, delay, load) determine whether the metric
>> via
>> > >Router1-Router2-Router3 is better Router1s direct T-1 (and given
>> > >load).
>> > >
>> > >
>> > >ROUTER1#show int serial5/0
>> > >Serial5/0 is up, line protocol is up
>> > > MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec, rely 255/255, load
1/255
>
>> > >
>> > >ROUTER2#show int faste0/0
>> > >FastEthernet0/0 is up, line protocol is up
>> > > MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load
>1/255
>> > >
>> > >ROUTER3#show int pos5/0/0
>> > >POS5/0/0 is up, line protocol is up
>> > > MTU 4470 bytes, BW 155000 Kbit, DLY 100 usec, rely 255/255, load
>3/255
>> > >
>> >Router4#show int faste5/1/0
>> >FastEthernet5/1/0 is up, line protocol is up
>> > MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load
1/255
>> >
>> > >
>> > >
>> > >! Router1 a direct T-1 to destinateion with metric 2181634
>> > >router1#show ip route x.y.z.a
>> > >Routing entry for x.y.z.a/24
>> > > Known via "eigrp 260", distance 110, metric 2181634, type internal
>> > > Redistributing via eigrp 120
>> > > Last update from x.y.z.b on Serial3/2, 00:33:11 ago
>> > > Routing Descriptor Blocks:
>> > > * x.y.z.b, from x.y.z.b, 00:33:11 ago, via Serial3/2
>> > > Route metric is 2181634, traffic share count is 1
>> > > Total delay is 20200 microseconds, minimum bandwidth is 1544
Kbit
>> > > Reliability 255/255, minimum MTU 1500 bytes
>> > > Loading 7/255, Hops 2
>> > >
>> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:53 GMT-3