By far my worst experience of all . The authentication part .. it took me 4 hrs to complete a silly task to config authentication .. not that i dont know topic due to careless ness and lack of bloody concentration … in fact so many time after repeating the same mistake , i still configured and got used to autonomous system 1 and this made me mad and configured the , but the required was for autonomous 100 i still feel ashamed to configure that badly .. so when you do please be careful about the autonomous system number
#EIGRP AUTHENTICATION SUNDAY DEC 28 2008#
IP AUTHENTICATION KEY-CHAIN EIGRP:
To enable authentication of EIGRP packets, use the “ip authentication key-chain eigrp” in interface config mode
To configure the hello interval for EIGRP routing process designated by a AS number , use the “ip hello-interval eigrp” command in interface config mode
“ip hello-interval eigrp as-number seconds”
Defaults:
For low-speed , NBMA network 60 seconds For all other network , 5 seconds
Usage Guidelines:
The default of 60 seconds applies only to low-speed , NBMA media
Low speed is considered to be a rate of T1 or slower, as specified with the “bandwidth” interface config command.
Note that for the purposes of EIGRP, Frame relay , and Switched Multimedia Data Service (SMDS) networks may be considered to be NBMA.
These networks are considered NBMA if the interface has not been configured to use physical multicastion, otherwise , they are considered to be NBMA
#IP HOLD-TIME EIGRP#:
IP HOLD-TIME:
To configure the hold time for a particular EIGRP routing process designated by the AS number , use the “ip hold-time eigrp” command in interface config mode
“ip hold-time eigrp as-number seconds”
DEFAULTS:
For low speed , nonbroadcast multiaccess (NBMA) networks : 180 seconds For all other networks : 15 seconds
Usage Guidelines:
On every congested and large networks , the default hold time might not be sufficient time for all routers and access to servers to recieve hello packets from their neighbors.
In this case , you may want to increase the hold time
We recommend that hold the hold time be at least three times the hello interval if a router does not recieve a hello packet within the specified hold time, routes through this router are considered unavailable
Increasing the hold time delays route convergence accross the network
The default of 180 seconds hold time and 60 seconds hello interval apply only to low-speed, NBMA media.
#IP-HELLO INTERVAL EIGRP IE VOL 4.10#
IP-HELLO INTERVAL EIGRP :
To configure the hello interval for EIGRP routing process designated by a AS number , use the “ip hello-interval eigrp” command in interface config mode
“ip hello-interval eigrp as-number seconds”
Defaults:
For low-speed , NBMA network 60 seconds For all other network , 5 seconds
Usage Guidelines:
The default of 60 seconds applies only to low-speed , NBMA media
Low speed is considered to be a rate of T1 or slower, as specified with the “bandwidth” interface config command.
Note that for the purposes of EIGRP, Frame relay , and Switched Multimedia Data Service (SMDS) networks may be considered to be NBMA.
These networks are considered NBMA if the interface has not been configured to use physical multicastion, otherwise , they are considered to be NBMA
#IP HOLD-TIME EIGRP#:
IP HOLD-TIME:
To configure the hold time for a particular EIGRP routing process designated by the AS number , use the “ip hold-time eigrp” command in interface config mode
“ip hold-time eigrp as-number seconds”
DEFAULTS:
For low speed , nonbroadcast multiaccess (NBMA) networks : 180 seconds For all other networks : 15 seconds
Usage Guidelines:
On every congested and large networks , the default hold time might not be sufficient time for all routers and access to servers to recieve hello packets from their neighbors.
In this case , you may want to increase the hold time
We recommend that hold the hold time be at least three times the hello interval if a router does not recieve a hello packet within the specified hold time, routes through this router are considered unavailable
Increasing the hold time delays route convergence accross the network
The default of 180 seconds hold time and 60 seconds hello interval apply only to low-speed, NBMA media.
# EIGRP VARIANCE_DOC USAGE AND IE LAB VOL 4.10 MODULE SAT DEC 27 2K8#
VARIANCE (EIGRP):
To control load balancing in an internetwork based on the EIGRP , use the variance command in router config mode.
USAGE GUIDELINES:
Setting a variance value enables EIGRP to install multiple loop-free routes without unequal cost in a local routing table.
A route learned through EIGRP must meet two criteria to be installed in the local routing table
The route must be loop-free. This condition is satisfied when the reported distance is less than the total distance or when the route is fs.
The metric of the route must be lower than the metric of the best route multiplied by the variance configured on the router
NOTE: EIGRP does not load-share between multiple route; it only installs the routes in the local routing table.
Then, the local routing table enables switching hardware or software to load-share between the multiple paths
CODE
r4#sir 155.0.5.0 Routing entry for 155.0.5.0/24 Known via “eigrp 100″, distance 90, metric 10639872, type internal Redistributing via eigrp 100 Last update from 155.0.45.5 on Serial0/1, 00:02:34 ago Routing Descriptor Blocks: 155.0.45.5, from 155.0.45.5, 00:02:34 ago, via Serial0/1
Route metric is 40640000, traffic share count is 21————->$$$$$$$$$
Total delay is 25000 microseconds, minimum bandwidth is 64 Kbit Reliability 255/255, minimum MTU 1500 bytes Loading 1/255, Hops 1 * 155.0.0.5, from 155.0.0.5, 00:02:34 ago, via Serial0/0
Route metric is 10639872, traffic share count is 80—————>$$$$$$$$$
Total delay is 25000 microseconds, minimum bandwidth is 256 Kbit Reliability 255/255, minimum MTU 1500 bytes Loading 1/255, Hops 1
FORGOT to mention there were instances where i played with “TRAFFIC SHARE MIN” and “traffic share balanced” commands ..
#EIGRP NEIGHBOR COMMAND FRI DEC 26 IE VOL 1 VER 4.10#
NEIGHBOR (EIGRP):
To define a neighboring router with which to exchange routing information on a router that is running EIGRP , use the neighbor command in router config mode
Usage Guidelines: Multiple neighbor statements can be used to establish peering sessions with specific EIGRP neighbors
The interface through which EIGRP will exchange routing updates must be specified in the neighbor statement.
The interfaces through which two EIGRP neighbors exchange routing updates must be configured with IP addresses for the same network
Configuring the “passive-interface” command suppresses all incoming and outgoing updates and hello messages.
EIGRP neighbor adjacencies cannot be established or maintained over an interface that is configured as passive
these are my doc cd references as topologies are very minor and easy to catch up
#IP-HELLO INTERVAL EIGRP IE VOL 4.10#
IP-HELLO INTERVAL EIGRP :
To configure the hello interval for EIGRP routing process designated by a AS number , use the “ip hello-interval eigrp” command in interface config mode
“ip hello-interval eigrp as-number seconds”
Defaults:
For low-speed , NBMA network 60 seconds For all other network , 5 seconds
Usage Guidelines:
The default of 60 seconds applies only to low-speed , NBMA media
Low speed is considered to be a rate of T1 or slower, as specified with the “bandwidth” interface config command.
Note that for the purposes of EIGRP, Frame relay , and Switched Multimedia Data Service (SMDS) networks may be considered to be NBMA.
These networks are considered NBMA if the interface has not been configured to use physical multicastion, otherwise , they are considered to be NBMA
#IP HOLD-TIME EIGRP#:
IP HOLD-TIME:
To configure the hold time for a particular EIGRP routing process designated by the AS number , use the “ip hold-time eigrp” command in interface config mode
“ip hold-time eigrp as-number seconds”
DEFAULTS:
For low speed , nonbroadcast multiaccess (NBMA) networks : 180 seconds For all other networks : 15 seconds
Usage Guidelines:
On every congested and large networks , the default hold time might not be sufficient time for all routers and access to servers to recieve hello packets from their neighbors.
In this case , you may want to increase the hold time
We recommend that hold the hold time be at least three times the hello interval if a router does not recieve a hello packet within the specified hold time, routes through this router are considered unavailable
Increasing the hold time delays route convergence accross the network
The default of 180 seconds hold time and 60 seconds hello interval apply only to low-speed, NBMA media.
#IP-HELLO INTERVAL EIGRP IE VOL 4.10#
IP-HELLO INTERVAL EIGRP :
To configure the hello interval for EIGRP routing process designated by a AS number , use the “ip hello-interval eigrp” command in interface config mode
“ip hello-interval eigrp as-number seconds”
Defaults:
For low-speed , NBMA network 60 seconds For all other network , 5 seconds
Usage Guidelines:
The default of 60 seconds applies only to low-speed , NBMA media
Low speed is considered to be a rate of T1 or slower, as specified with the “bandwidth” interface config command.
Note that for the purposes of EIGRP, Frame relay , and Switched Multimedia Data Service (SMDS) networks may be considered to be NBMA.
These networks are considered NBMA if the interface has not been configured to use physical multicastion, otherwise , they are considered to be NBMA
#IP HOLD-TIME EIGRP#:
IP HOLD-TIME:
To configure the hold time for a particular EIGRP routing process designated by the AS number , use the “ip hold-time eigrp” command in interface config mode
“ip hold-time eigrp as-number seconds”
DEFAULTS:
For low speed , nonbroadcast multiaccess (NBMA) networks : 180 seconds For all other networks : 15 seconds
Usage Guidelines:
On every congested and large networks , the default hold time might not be sufficient time for all routers and access to servers to recieve hello packets from their neighbors.
In this case , you may want to increase the hold time
We recommend that hold the hold time be at least three times the hello interval if a router does not recieve a hello packet within the specified hold time, routes through this router are considered unavailable
Increasing the hold time delays route convergence accross the network
The default of 180 seconds hold time and 60 seconds hello interval apply only to low-speed, NBMA media.
I WAS FACING TROUBLE WITH FRAME-RELAY CONFIGURATION AND COULDNT RECOLLECT IT .. I HAVE MADE A SMALL EFFORT TO REMEMBER SOME CORE CONCEPTS .. ENJOY IF ITS INTERESTING , ENJOY EVEN IF IT IS BORING !.!.! 3 PACKET SUCCESS
#CONFIGURING FRAME-RELAY START(FRS) AND END POINTS
Configuration:
let us take this present situation where in we have 3 interfaces s0/0 s0/1 s0/2 for frs and connected to other routers respectively
first we will go about configuring the framerelay switch or in our case making router as a frs
first , imagine that you are literally sitting on the interface s0/1 which connects to routers s0/0 and has dlci’s 104 and 105
That router will be the hub and other two will be spokes with dlcis 501 and 401 for s0/2 and s0/0 interfaces respectively
Now imagine that you are on s0/1 of the frs and router a has thrown a packet for dlci 501 . as you are a frs you need to route that particular packet to that dlci
The first thing we will look after accepting packet for routing is to route the packet or throw the packet to an interface which has nearest target address
Next as we are on a frame-relay network we need to also see the incoming dlci and also outgoing dlci by sitting on the router interface .. its so much fun to sit on the network card and route packets ….! (oops 4 packets missed)
So , we see that packet is coming from a dlci 105 which needs to be routed to 501 and it has a nearest interface of s0/2 that this frs connects to.
That’s it you are done configuring it … just remember these things
now see here we are sitting on serial0/1 and a packet came begging.. we have considered it and accepted to route the packet to destination dlci 501 . the packet came from 105 dlci . after calculations or analysations we knew that s0/2 was very much near to the r5 or 501 dlci
Now similarly ,
how did router at hub knew that it should foreward packet to 501 dlci and to that particular ip ????
sit on router1 which is a hub and has two dlcis as it sees , 104 and 105
how could it see two dlci’s .. or how could we see two dlcis from router 1 or hub …. sadistic laugh .. we have already configured it ..!.. (oops middle packet was successful)
we need to map some of the dlci’s to the ip addresses of the remote routers . simple then whenever we want any thing to be forewarded to a ip we will foreward it to dlci and then dlci will take care . just and imagination
so , keep in mind route is word which is confined to frs and map is a word which is confined to the end points
interface Serial0/0 ip address 10.0.0.1 255.0.0.0 encapsulation frame-relay no ip split-horizon eigrp 1 clock rate 2000000 frame-relay map ip 10.0.0.1 104 frame-relay map ip 10.0.0.4 104 broadcast frame-relay map ip 10.0.0.5 105 broadcast no frame-relay inverse-arp !
as you can see whenever we want anything sent for 10.0.0.5 we want it go to dlci 105 which will then be converted by our frs .. a similar config should be done at r5 and bingo we can establish connectivity
I was confused with fr so though of putting it some or the other way .. though it needs some of the other configs these are the base level configs and should help you to reach to max without much of the confusion
1.To enable EIGRP split horizon, use ip split-horizon eigrp as-no
2. For networks that include x.25 and psn PACKET SWITCHED NETWORKS,you can use neighbor router configuration to defeat split horizon
3. As an alternative, you can explicitly specify the “no ip split-horizon eigrp” command in the config
CODE
r1#show ip int s0/0 | i Split Split horizon is disabled
r5#show ip route Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2 E1 – OSPF external type 1, E2 – OSPF external type 2 i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2 ia – IS-IS inter area, * – candidate default, U – per-user static route o – ODR, P – periodic downloaded static route
Gateway of last resort is not set
D 1.0.0.0/8 [90/2195456] via 10.0.0.1, 00:46:06, Serial0/0 D 4.0.0.0/8 [90/2707456] via 10.0.0.1, 00:41:54, Serial0/0 C 5.0.0.0/8 is directly connected, FastEthernet0/0 C 10.0.0.0/8 is directly connected, Serial0/0 r5#ping 4.0.0.4
Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 4.0.0.4, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 12/20/28 ms r5#ping 1.0.0.1
Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 1.0.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 12/15/24 ms r5#
1. To allow automatic summaraisation of subnet routes into network-level routes, use the auto-summary command in boundaries in router config mode
2. To disable this function and send subprefix routing information accross classful network boundaries , use the no form of this command
USAGE GUIDELINES
1. Route summaraisation reduces the amount of routing info in the routing tables
2. By default BGP does not accept subnets redistributed from and IGP
3. To allow the software to create summary subprefixes to the classful network boundary , use auto-summary command
4. To advertise and carry subnet routes in BGP, use an explicit network comamnd because automatic summary is disabled by default
5. If you have not enetered a network command, you will not advertise network routes for networks with subnet routes unless they contain a summary route
6. EIGRP summary routes are given an AD of 5
7. RIP V1 uses automatic summaraisation . If you are using RIPV2 ,you can turn off auto summary by specifying the no auto-summ
8. Disable automatic summaraisation if you mutst perform routing between disconnected subnets. When automatic summaraisatin is off , subnets are advertised
1. When the network command is configured for an EIGRP routing process the router matches one or more local interfaces
2. The network command will match only local interfaces that are configured with addresses that are within the same subnet as the addresses that has been configured with the network command
3. The router will then establish the neighbors through the matched interfaces.
4. There is no limit to the number of network statements that can be configured on a router
