MY CCIE JOURNEY

with the above link did you compare with the following the topology table ..

r3#sie top all-links
IP-EIGRP Topology Table for AS(100)/ID(10.1.3.9)

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status

P 10.1.3.8/30, 1 successors, FD is 128256, serno 5
via Connected, Loopback39
P 10.1.2.8/30, 1 successors, FD is 40640000, serno 13
via 10.1.203.1 (40640000/128256), Serial1/1
via 10.1.103.1 (41152000/40640000), Serial1/0
P 10.1.1.8/30, 1 successors, FD is 40640000, serno 9
via 10.1.103.1 (40640000/128256), Serial1/0
via 10.1.203.1 (41152000/40640000), Serial1/1
P 10.1.3.0/30, 1 successors, FD is 128256, serno 3
via Connected, Loopback31
P 10.1.2.0/30, 1 successors, FD is 40640000, serno 11
via 10.1.203.1 (40640000/128256), Serial1/1
via 10.1.103.1 (41152000/40640000), Serial1/0
P 10.1.1.0/30, 1 successors, FD is 40640000, serno 7
via 10.1.103.1 (40640000/128256), Serial1/0
via 10.1.203.1 (41152000/40640000), Serial1/1
P 10.1.3.4/30, 1 successors, FD is 128256, serno 4
via Connected, Loopback35
P 10.1.2.4/30, 1 successors, FD is 40640000, serno 12
via 10.1.203.1 (40640000/128256), Serial1/1
via 10.1.103.1 (41152000/40640000), Serial1/0
P 10.1.1.4/30, 1 successors, FD is 40640000, serno 8
via 10.1.103.1 (40640000/128256), Serial1/0
via 10.1.203.1 (41152000/40640000), Serial1/1
P 10.1.103.0/29, 1 successors, FD is 40512000, serno 1
via Connected, Serial1/0
P 10.1.102.0/29, 2 successors, FD is 41024000, serno 10
via 10.1.103.1 (41024000/40512000), Serial1/0
via 10.1.203.1 (41024000/40512000), Serial1/1
P 10.1.203.0/29, 1 successors, FD is 40512000, serno 2
via Connected, Serial1/1

now did you get the difference ?????


this is where i struck for max amount of time ..the damn ip cef command and its out put ...

Recent Cisco IOS releases have Cisco Express Forwarding (CEF) enabled by
default. CEF allows fast switching of packets based on a per-destination
switching architecture. The first packet in a flow is routed, and the rest are
switched. This is the preferred behavior in most circumstances, because it
allows load balancing in fast-switching architectures.

Note: Typically, you would not disable CEF in a production network. It is done
here only to illustrate load balancing.

and the other stuff is as usual .. the variance command along unequal load balancing as everyone of us would know ..

catch you with more updates

ciao...

regards
Rakesh

Essentially, EIGRP’s DUAL state machine has just computed the topology table
for these routes and installed them in the routing table.



r1(config-router)#network 10.0.0.0
r1(config-router)#
*Mar 1 00:17:27.779: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor 10.1.103.2 (Serial1/1) is up: new adjacency
*Mar 1 00:17:27.991: IP-EIGRP(Default-IP-Routing-Table:100): Processing incoming UPDATE packet
*Mar 1 00:17:27.995: IP-EIGRP(Default-IP-Routing-Table:100): 10.1.102.0/29 - do advertise out Serial1/1
*Mar 1 00:17:27.995: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.102.0/29 metric 40512000 - 40000000 512000
*Mar 1 00:17:27.999: IP-EIGRP(Default-IP-Routing-Table:100): 10.1.103.0/29 - do advertise out Serial1/1
*Mar 1 00:17:27.999: IP-EIGRP(Default-IP-Routing-Table:100): 10.1.1.0/30 - do advertise out Serial1/1
*Mar 1 00:17:27.999: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.1.0/30 metric 128256 - 256 128000
*Mar 1 00:17:28.003: IP-EIGRP(Default-IP-Routing-Table:100): 10.1.1.4/30 - do advertise out Serial1/1
*Mar 1 00:17:28.003: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.1.4/30 metric 128256 - 256 128000
*Mar 1 00:17:28.003: IP-EIGRP(Default-IP
r1(config-router)#-Routing-Table:100): 10.1.1.8/30 - do advertise out Serial1/1
*Mar 1 00:17:28.007: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.1.8/30 metric 128256 - 256 128000
*Mar 1 00:17:28.219: IP-EIGRP(Default-IP-Routing-Table:100): Processing incoming UPDATE packet
*Mar 1 00:17:28.219: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.203.0/29 M 41024000 - 40000000 1024000 SM 40512000 - 40000000 512000
*Mar 1 00:17:28.223: IP-EIGRP(Default-IP-Routing-Table:100): route installed for 10.1.203.0 ()
*Mar 1 00:17:28.223: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.3.0/30 M 40640000 - 40000000 640000 SM 128256 - 256 128000
*Mar 1 00:17:28.227: IP-EIGRP(Default-IP-Routing-Table:100): route installed for 10.1.3.0 ()
*Mar 1 00:17:28.227: IP-EIGRP(Default-IP-Routing-Table:100): Int 10.1.3.4/30 M 40640000 - 40000000 640000 SM 128256 - 256 128000
*Mar 1 00:17:28.231: IP-EIGRP(Default-IP-Routing-Table:100): route installed for 10.1.3.4 ()
*Mar 1 00:17:28.231: IP-EIGRP(Default-I
r1(config-router)#P-Routing-Table:100): Int 10.1.3.8/30 M 40640000 - 40000000 640000 SM 128256 - 256 128000

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


this is the neighbor table


r1#sie nei
IP-EIGRP neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 10.1.102.2 Se1/0 12 00:02:39 217 2280 0 8
0 10.1.103.2 Se1/1 13 00:02:53 150 2280 0 9


----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


this was one of the objective questions?

what happens when command network command is not given in eigrp ?

eigrp installs networks ..

and other crap options ..

so correct one is 1 option....

output of show ip route

10.0.0.0/8 is variably subnetted, 12 subnets, 2 masks
D 10.1.3.8/30 [90/40640000] via 10.1.103.2, 00:05:37, Serial1/1
D 10.1.2.8/30 [90/40640000] via 10.1.102.2, 00:05:37, Serial1/0
C 10.1.1.8/30 is directly connected, Loopback19
D 10.1.3.0/30 [90/40640000] via 10.1.103.2, 00:05:37, Serial1/1
D 10.1.2.0/30 [90/40640000] via 10.1.102.2, 00:05:37, Serial1/0
C 10.1.1.0/30 is directly connected, Loopback11
D 10.1.3.4/30 [90/40640000] via 10.1.103.2, 00:05:37, Serial1/1
D 10.1.2.4/30 [90/40640000] via 10.1.102.2, 00:05:37, Serial1/0
C 10.1.1.4/30 is directly connected, Loopback15
C 10.1.103.0/29 is directly connected, Serial1/1
C 10.1.102.0/29 is directly connected, Serial1/0
D 10.1.203.0/29 [90/41024000] via 10.1.103.2, 00:05:37, Serial1/1
[90/41024000] via 10.1.102.2, 00:05:37, Serial1/0

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

this is the output of tcl script and ping test ...

tclsh
foreach address {

10.1.1.1
10.1.1.5
10.1.1.9
10.1.102.1
10.1.102.2
10.1.2.1
10.1.2.5
10.1.2.9
10.1.203.1
10.1.203.2
10.1.3.1
10.1.3.5
10.1.3.9
10.1.103.1
10.1.103.2
} {
ping $address
}


r1#tclsh
r1(tcl)#tclsh

r1(tcl)#foreach address {
+>(tcl)#
+>(tcl)#10.1.1.1
+>(tcl)#10.1.1.5
+>(tcl)#10.1.1.9
+>(tcl)#10.1.102.1
+>(tcl)#10.1.102.2
+>(tcl)#10.1.2.1
+>(tcl)#10.1.2.5
+>(tcl)#10.1.2.9
+>(tcl)#10.1.203.1
+>(tcl)#10.1.203.2
+>(tcl)#10.1.3.1
+>(tcl)#10.1.3.5
+>(tcl)#10.1.3.9
+>(tcl)#10.1.103.1
+>(tcl)#10.1.103.2
+>(tcl)#} {
+>(tcl)#ping $address
+>(tcl)#}

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.9, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.102.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/140/256 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.102.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/52/172 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/90/172 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/46/116 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.2.9, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/52/116 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.203.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/55/108 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.203.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/68/204 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.3.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/82/208 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.3.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 16/65/92 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.3.9, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 52/93/208 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.103.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/71/188 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.103.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/69/160 ms
r1(tcl)#


ping successful....

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

a new command first of view is topology and then did you ever think about the links ad>fd? i had the same doubt .. and using the all links command you will get it without pain ....


P 10.1.3.8/30, 1 successors, FD is 40640000
via 10.1.103.2 (40640000/128256), Serial1/1
P 10.1.2.8/30, 1 successors, FD is 40640000
via 10.1.102.2 (40640000/128256), Serial1/0
P 10.1.1.8/30, 1 successors, FD is 128256
via Connected, Loopback19
P 10.1.3.0/30, 1 successors, FD is 40640000
via 10.1.103.2 (40640000/128256), Serial1/1
P 10.1.2.0/30, 1 successors, FD is 40640000
via 10.1.102.2 (40640000/128256), Serial1/0
P 10.1.1.0/30, 1 successors, FD is 128256
via Connected, Loopback11
P 10.1.3.4/30, 1 successors, FD is 40640000
via 10.1.103.2 (40640000/128256), Serial1/1
P 10.1.2.4/30, 1 successors, FD is 40640000
via 10.1.102.2 (40640000/128256), Serial1/0
P 10.1.1.4/30, 1 successors, FD is 128256
via Connected, Loopback15

Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status

P 10.1.103.0/29, 1 successors, FD is 40512000
via Connected, Serial1/1
P 10.1.102.0/29, 1 successors, FD is 40512000
via Connected, Serial1/0
P 10.1.203.0/29, 2 successors, FD is 41024000
via 10.1.102.2 (41024000/40512000), Serial1/0
via 10.1.103.2 (41024000/40512000), Serial1/1


Use the show ip eigrp topology
10.1.102.0/29 command to view the information EIGRP has received about the
route from R1 and R2.


r3#sie top 10.1.102.0/29
IP-EIGRP (AS 100): Topology entry for 10.1.102.0/29
State is Passive, Query origin flag is 1, 2 Successor(s), FD is 41024000
Routing Descriptor Blocks:
10.1.103.1 (Serial1/0), from 10.1.103.1, Send flag is 0x0
Composite metric is (41024000/40512000), Route is Internal
Vector metric:
Minimum bandwidth is 64 Kbit
Total delay is 40000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1
10.1.203.1 (Serial1/1), from 10.1.203.1, Send flag is 0x0
Composite metric is (41024000/40512000), Route is Internal
Vector metric:
Minimum bandwidth is 64 Kbit
Total delay is 40000 microseconds
Reliability is 255/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1



Several things to remember about the output of this command regarding EIGRP
are:
• Bandwidth metric represents minimum bandwidth over the path to the
destination network.
• Delay metric represents total delay over the path.
• MTU represents the minimum maximum transmission unit over the path.
• The hop count to a destination network is visible, which may prove
useful. If you do not have full knowledge of your network, you can still
check how many Layer 3 devices are between your router and the
destination network.


FEW CONFIGS TO FOLLOW

LAB 2.2 EIGRP LOAD BALANCING:

LEARNING OBJECTIVES:

1.Review basic eigrp configuration

2.explore the eigrp topology table

3.learn to identify successor, feasible successors and feasible distances

4.learn to use debug commands for eigrp topology table

5.configure and verigy equal cost load balancing with eigrp

6.configure and verify unequal cost load balancing with eigrp




















SCENARIO:

As a senior network engineer you are considering deploying eigrp in your corporation. you are also interested in equal cost and unequal
cost load balancing because your network is filled with redundant links these links are not often used by other link state protocols
because of high metrics . since you are interested in testing eigrp claims that you have read about.you decide to implement and test on
a set of three lab routers before deploying eigrp throughout your corporate network ...


the following is the topology



the following are the lab router configs

STRATEGIES IMPLEMENTED :

from this lab onwards i have changed the way to represent diagrams ...

1. use colors for practising ...

2. blue pen for router symbols

3.dark brown sketch for router naming

4.green sketch for serial interfaces

5.blue sketch for fa interfaces connection

6.red for ip address and interface naming ...

i would have used more but read an article by one of ccie that he lost time in making more and more colorful .. i will stick to these colors till my ccie.. i may scan one copy and upload it so that any one reading it would get a basic idea .. if at all you need scanned copy let me know through a pm.

THE WAY I CONFIGURED :

intially i have made configs like logg sync and aliases in a notepad and copied it to all routers after that i went to induvidaul routers

1.firstly i went to router 1

2.configured loopbacks

3. configured fa

4. configre serial

5.enable eigrp

so in this way i went on ...



the student guide was in nuts and was configuring induvidually .. i dint liked it and so i went on my own

PROBLEMS I FACED:

1.FIRSTLY when i configured this and was testing for convergence by shutting down one of fa interface i never saw it .. some thing wrong with gns3 or may with my configs

2.idiotic ping stoppage .. i gave a repeated ping #ping 10.1.1.1 repeat 10000 for seeing the interface and its properties and i never knew how to stop the dirty ping .. i had to restart the router 3 to 4 times for this .. later i knew the command to stop ping was ctrl + ^ combination

over and out for lab 2.2

REGARDS
Rakesh

This is the lab topology with configs ..... i do paste this configs because its a kind of back up for me and its a kind of good practise for people who try in future to just copy and paste these configs...

















so to start of with this is the topology ... this is straight from cisco lab guide edition version 5 bsci ...

theres a mistake in printing ip addresses 10.1.100.0/24 belongs to fa0/0 of r1
10.1.200.0/24 belongs to s1/0 of r1



so to start of with the given question and objectives :

LAB 2-1

LEARNING OBJECTIVES

1.Configuring EIGRP on an Interface

2.Configuring Bandwidth command to limit Eigrp bandwidth

3.verify Eigrp adjacencies

4.verify eigrp routing info exchage

5.utilize debugging commands for troubleshooting EIGRP

6.CHALLENGE: TEST covergence when topology change occurs



SCENARIO

You are responsible for configuring the new network to connect your companys engineering , Marketing and accounting departments
represented by loop back interfaces on three routers . the physical devices have just been installed and connected by fast ethernet
and serial cables . Your task is to configure eigrp to enable full connectivity between all departments


i will be following by my ideas , staratagies and way i thought and problems faced after this message .. so these are the configs

config for R1

Sight of relief ..

Today again after two horrible waste of days was finally on track... i started with cisco student lab guide and started the all new first step that is the TCL SCRIPT to ping all the interfaces .. here is the overview .


The Following is the toplogy




















A SIMPLE DEMONSTRATION

in order to ping all of the interfaces at once ... you can use the tcl script and ping them

let us say you router is r0 and you want to ping 4 ip addresses(1.0.0.1 1.0.0.2 1.0.0.3 1.0.0.4) at a time


R0#tclsh
R0(tcl)# foreach address {
+>(tcl)#1.0.0.1
+>(tcl)# 1.0.0.2
+>(tcl)# 1.0.0.3
+>(tcl)# 1.0.0.4

+>(tcl)# } {
+>(tcl)# ping $address
+>(tcl)#}

you can ping as many addresses you have at one shot ...


the simplest thing to do is to write down in a note pad and copy paste in router ...

i advice the users who are using and seeing this for the first time to do it by hand in router to feel and see how prompts change ...
the two router configs will be pasted after this ,, i will list out the ip address first to use it in tcl script

1.0.0.1
1.0.0.2
2.0.0.1
2.0.0.2
3.0.0.1
3.0.0.2
4.0.0.1
4.0.0.2
5.0.0.1
5.0.0.2
6.0.0.1
6.0.0.2
7.0.0.1
7.0.0.2

as you might have imagine i need to change the prompt and ping 14 times which is not easy and time wasting ..

so this how script goes ...

open a note pad

tclsh
foreach address {
2.0.0.1
2.0.0.2
3.0.0.1
3.0.0.2
4.0.0.1
4.0.0.2
5.0.0.1
5.0.0.2
6.0.0.1
6.0.0.2
7.0.0.1
7.0.0.2
} {
ping $address
}

now at router prompt just copy the things in note pad and paste it into the router .. the following result if everthing done correctly should be appearing or ping wont be successful at the interfaces misconfigured

this is my output when executed on r1..

[code]r1(tcl)#tclsh

r1(tcl)#foreach address {
+>(tcl)#2.0.0.1
+>(tcl)#2.0.0.2
+>(tcl)#3.0.0.1
+>(tcl)#3.0.0.2
+>(tcl)#4.0.0.1
+>(tcl)#4.0.0.2
+>(tcl)#5.0.0.1
+>(tcl)#5.0.0.2
+>(tcl)#6.0.0.1
+>(tcl)#6.0.0.2
+>(tcl)#7.0.0.1
+>(tcl)#7.0.0.2
+>(tcl)#} {
+>(tcl)#ping $address
+>(tcl)#}

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/52/112 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2.0.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/69/140 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 3.0.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/8 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/108/284 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 4.0.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/49/104 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 5.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/48/116 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 5.0.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/99/200 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 6.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/53/144 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 6.0.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/66/196 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 7.0.0.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/88/160 ms
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 7.0.0.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/58/172 ms
r1(tcl)#


so this is the power of the script ... now to try my configs

directly open a router and paste my router 1 and router 2 configs and dont forget to manually reup the interfaces as they are in shutdown mode


CONFIG FOR R1
interface FastEthernet0/0
ip address 2.0.0.2 255.255.255.252
duplex auto
speed auto
!
interface FastEthernet0/1
ip address 3.0.0.2 255.255.255.252
duplex auto
speed auto
!
interface Serial1/0
ip address 4.0.0.2 255.255.255.252
serial restart-delay 0
!
interface Serial1/1
ip address 5.0.0.2 255.255.255.252
serial restart-delay 0
!
interface Serial1/2
ip address 6.0.0.2 255.255.255.252
serial restart-delay 0
!
interface Serial1/3
ip address 7.0.0.2 255.255.255.252
serial restart-delay 0
!
ip http server
!
!
!
!
control-plane
!
!
line con 0
logging synchronous
line aux 0
line vty 0 4
!
!
end

CONFIG FOR R0
[code]interface FastEthernet0/0
ip address 2.0.0.1 255.255.255.252
duplex auto
speed auto
!
interface FastEthernet0/1
ip address 3.0.0.1 255.255.255.252
duplex auto
speed auto
!
interface Serial1/0
ip address 4.0.0.1 255.255.255.252
serial restart-delay 0
!
interface Serial1/1
ip address 5.0.0.1 255.255.255.252
serial restart-delay 0
!
interface Serial1/2
ip address 6.0.0.1 255.255.255.252
serial restart-delay 0
!
interface Serial1/3
ip address 7.0.0.1 255.255.255.252
serial restart-delay 0
!
ip http server
!
!
!
!
control-plane
!
!
line con 0
logging synchronous
line aux 0
line vty 0 4
!
!
end


TCL NOTEPAD
tclsh
foreach address {
2.0.0.1
2.0.0.2
3.0.0.1
3.0.0.2
4.0.0.1
4.0.0.2
5.0.0.1
5.0.0.2
6.0.0.1
6.0.0.2
7.0.0.1
7.0.0.2
} {
ping $address
}




this is the reference from cisco website and number . tcl is valid from 12.3 ios and surprisingly i couldnt find it in 12.4 13b of 3660 so i executed on 3775

hxxp://www.cisco.com/web/about/security/intelligence/securetcl.html

regards
Rakesh

The two of the points were not comfortable for me and while i was going through the student guide i got them cleared after a second read

1.The hello packets contains all the k values in its and in this way router exchanging hello packets with other can decide on the fly the kvalue mismatch

2.Eigrp 32-metric representation is granular ...

Well granular was ok with grammer but what about 32 .. where is that used or where is that represented i was thinking to put a query packet in the forum for answer discover (see iam getting so much in to subject lol)

and while i saw this during metric calculation i was enlightened ...

it means the eigrp metric ranges from 1 to 4294967296 ...this seems wierd right

now see this 2^32 = 4294967296... i was happy and hence completed

Todays and tomorrow plan is simple and walk in the park its the configuration part ...

so i will get through it quickly and luckily i found bsci lab edtion guide i will play with it and i will also paste the topology and config files so that any one reading it would be most benefited ..

regards
Rakesh

As mentioned i was going through wide variety of topics from student guide and came across different types of eigrp packets ... i could understand from cisco press the implementation part so i set up a lab in gns3 and ran wireshark packet capture utility .. the following are the results and i have now got the jist of packet generation i suppose ...still left out with some sort of packet types though..

this is the topology



















now this is the first capture screen shot this is from r0 - r1





















as you can see there are many important details to be observed let us see it one by one


1.first of all we can see the packet type "HELLO" and eigrp multicast address 224.0.0.10

2.the source address

3.in the bottom pane when you obseve carefully (EIGRP PARAMETERS ALL THE K'S AND THEIR VALUES )

4.also the holddown timer with ios version and eigrp revision version


r1 - r2 packet capture




















1.In this case you can see so many of the packets being generated understandably...

2.the keep alive packets can also be seen with few of the cdp enquires

3.even in this case the source is mentioned to perfection



There are few of the packets like update, acknowledgements
















update packets views

few of the interesting points

1.the only packets i couldnt see were query packets , i forced the middle router to be stub so that there would be a chance in generation of query packets
the out of querys can be seen in router console but not in capture packet session

2.there were no packet capture between fa0/0 and fa0/0 or r0 - r3 .. i thought i would get hello packets but i couldnt ..

these were some of the interesting stuff i found out in this session ..

today i will complete off with lesson and follow up with the updates ..


regards
Rakesh





**IF IAM WRONG OR MISINTERPRETED ANY WHERE PLEASE CORRECT ME ....
[/quote]

MULTIPLE NETWORK LAYER SUPPORT

• Eigrp supports IP, APPLETALK and Novell Netware Internet packet exchange(IPX) through the use of PROTOCOL DEPENDANT MODULES

• Eigrp does not require any special configuration to work across Layer2 Protocols

• ospf uses different configuration for different Layer2 Protocols , such as Ethernet and Frame-relay

• Eigrp represent values in 32 bit format for additional granularity

1. Neighbor discovery / recovery
2. Reliable Transport Protocol RTP
3. DUAL finite state machine
4. Protocol Dependant Modules (PDM'S)
   

• Guaranteed ordered delivery of EIGRP packets .

• Intermixed transmission of Multicast and Unicast Packets
  

• Responsible for network layer Protocol Specific requirements

• IP Eigrp module is responsible for sending and receiving eigrp pakects that are encapsulated in IP

• The ip-eigrp also responsible for parsing Eigrp Packets and informing DUAL of the new Information received
  

• Ip-eigrp asks Dual to make routing decisions , the results ofwhich are stored in ip routing table

• Ip-eigrp is responsible for re-distributing routes learned by other ip routing protocols

• AD = cost of next hop router and destination

• FD = cost from local router + cost between Local router and next hop router

• A Recomputation occurs when destination has no Feasible Successor
  

• Recomputation is the way to determine new successor when feasible successor are absent
  

• Recomputation is not processor intensive
  

• Its always better to avoid Re-Computation

• In the process , if the neighbor router has a route for destination , it sends a reply packet

• If it does not have a router it sends QUERY packet
  

• While the destination in active state , a router cannot change the Destination routing table information

Well as i have planned i have completed the modules from cbt nuggets and planned for BSCI student edition from cisco press..

All i can say is there is a huge huge difference between cbt nuggets and student edition from cisco press ..

cbt primarily concentrates on lab part and good real world examples .

student guide edition covers the best of the theory part that we have never seen in cbt .

i would highlight some of the points from eigrp session i had last night.

Hai everyone .... While seeing CBT NUGGETS i saw the access server which is being used by mr.jermy ciora. It was always fascinating to me and wanted to set up one .. i was struggling and struggling and i finally got it today . iam happy now ..

The entire credit goes to Mr.Rajendra for letting me know how to set up the access server and guiding me .. he is presently residing in banglore and you can reach him at rajendra.gps@gmail.com

To define an access server in my words..it simplest of server setups where in you can bounce from one router console to other router console without changing windows or tabs ...if you find any difficulty follow this tutorial and by the end you will know what exactly is an access server

The following is the simplest of topologies set up in my lab in gns3


























ip host ACCESSSERVER 2004 1.0.0.1 -------------------------------------------->[note the console port number from 'list' command ]


Configure the following on Your AccessServer...

------------------------------------------------------------------------------------------------
ip host R1 2001 1.0.0.1
ip host R2 2002 1.0.0.2
!
!
!
interface FastEthernet0/0
ip address 1.0.0.2 255.255.255.0
duplex auto
speed auto
!

ip route 0.0.0.0 0.0.0.0 1.0.0.1
line con 0
logging synchronous
line aux 0
line vty 0 4
no login
!
!
end

so start off thats it

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
accessserver#r1
Trying R1 (1.0.0.1, 2001)... Open
Connected to Dynamips VM "R1" (ID 1, type c3600) - Console port

#############################

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

*Mar 1 00:00:10.519: %SNMP-5-COLDSTART: SNMP agent on host r1 is undergoing a cold start
r1>enable
r1# -------> [the most important step i was struggling here to get back to access server but how ???? solution is to pm unborn hehe
i tried for an hour and searched even google dint found it so again pmed unborn]

[hit ctrl + shift + 6 key combination first then after that press 'x' you will be
back to you access server]

accessserver#

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

accessserver#r2
Trying R2 (1.0.0.1, 2002)... Open
Connected to Dynamips VM "R2" (ID 2, type c3600) - Console port


-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

r2>enable
r2#
r2#
accessserver#

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


now after loggin once .. check your access server for sessions for every session instance there will be a number . so pressing that number will be enough
to log our way into the router

accessserver#show session
Conn Host Address Byte Idle Conn Name
1 r1 1.0.0.1 0 5 r1
* 2 r2 1.0.0.1 0 1 r2


press 1 for r1 or 2 for r2

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

accessserver#1
[Resuming connection 1 to r1 ... ]

r1#


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

tip here is for r1 if you wanna have a number one session start the r1 first and later r2 so that session will be appropriate




ps. any one having doubts on settinup ms loop back adapter do msg me i will come back to soon...
and also test this

This completes the configuration & setting part.

Now try the connectivity between your AccSrv & PC. Open a command prompt & try pinging the Router Eth. interface 1.0.0.2

Console to the router & ping ur Loopback interface 10.0.1.

If you are able to ping, you are ready to go. Start rest of the routers & From the console window of AccSrv Type R0.......................... See the Magic (This is reverse telnet)


Regards
Rakesh ;)