Its been a while  

Tuesday, January 27, 2009

Hello everyone ... its been a while i wrote about my prep path .. it has also some thing to do with my exams going on and iam in a verge of creating / launching a website which will be uniqe .. so iam into learning the content management system joomla . so had to stop my prep and concentrate on making the website look and feel good ...


Presently we are a team of two members and the website concept is uniqe .. I need more of the elite members to join me and also aditionally to gain some rep in the community ...

anyways , joining in a team doesnt involve or doesnt require any one to any of the scripting skills / programming skills ... they just need to have good ability to pick some articles and choose the best of the articles ...

the majority of the concept being to make a free emag which will be available to all people with photos of our team members .. the website is official and no warez stuff which will make us proud to be part of the team

And lot of other goals and plans which cannot be disclosed as of now .. so , guys if you are interested and have some time to contribute please let me know at

raaki_88@yahoo.com

so the prep update will be stopped for another week or so .. any ways got to go and work on it ..

good day

regards
rakesh

Started with ospf  

Monday, January 19, 2009

Started with ospf and done with video 1 from cbtt nugets ... also wanted to revise and go from the ground level so went on with the part 1 of laura chappels course and started with arp .. i have got so much of stuff but never had fun using them .. iam utilising them now a days boy iam happy ..

so to start of with ospf nothing complicated to explain or revise until the other two videos

on to laura chappel well the concept was on arp and now i could understand what is arp , why it cannot be forewarded accross routers etc

main concepts involve

gratituos arp

proxy arp

and arp headers

gratituos arp is nothing but a arp packets which checks and validates the ip address given to the system is not given for any other system . this is done by sending a arp packet which contains its own ip address , so if a duplicate system is present it responds to it so that it can be corrected

proxy arp if we know about router converting or routing different netwoks its the same , the router gives its own mac address of the interface without forewarding the broadcast as arp is based on broadcast

arp headers dosent contain any info on protocols such as tcp udp and ip headers so it basically cannot be read by devices which looks for ip headers


this is to sum up

Lab 4:  

It's been a while .. i went on a holiday and hell i did enjoy a lot ... hehe cant reveal it though laugh.gif ... any ways i wanted to inform you with the left out labs from foundation gap and also holiday thing but couldnt as sadikhov was down and i couldnt write them down ..

our college has given us holidays for a week and in the mean while we planned for a holiday spot which is full of green stuff and beach to surround ... ohh i want to work as a fisher man over there ... holy hell ...

great ...

done with lab 4 and lab 5 from foundation gap

lab 4 :

loadbalancing .. ---> nothing great in this ---

covered commands -- > variance , traffic share count

timer manipulation .. --- > sia -- x minutes , disabling sia --- > can be done from router config mode > timer ?

lab 5:

authentication :

mode : mds5

key - chain config ...

on to ospf revising cbt.t as need a good amount of revision and should be strong at concepts as we dont know what else can change in near future laugh.gif

Having fun with basic clusters ...and GNS3  

Wednesday, January 7, 2009

Hai all , me and one of my pals named darlord (:0 alias exec darklord duplicatename) thought of building a minor cluster .. The idea was started by him and i downloaded and installed it .. and quick review

what is a cluster?

well iam not into clustering so i would define that its a group of computers connected and when booted with a cluster operating systems unites their resources and become one computer

In simple words :

consider two computer connected via a ethernet cable .. boot with cluster operating system and they will load balance and share the tasks

How did i do that ?

Well its a child play till now ... the best thing is labbing and for any thing any everything we can lab on vmware ..

The cluster operating system name is "cluster knoppix" a knoppix distribution .. feel free to google only 600 mb of cd

next create two vm's with "other linux 2.6.x" kernel and give the iso path to the cd rom in vmware and bingo you cluster is already booting ..


to make some sense in what iam talking see this screen shot



























now did you see two of the ip's of the vm's which has cluster knopppix os and console message "cluster has 2 members " ..

How does this help us ?


Dont you work with gns3 ...? ofcourse the answer is yes .... so when you happen to have some old computers and the unused ones or let us say you wanna add some power .. boot with cluster and bingo they share you cpu power and also efficiency

Note pad modularity .. cool as speed is essence  

Monday, January 5, 2009

This is the structural note pad i have been following hope this helps

its so flexible and any time you can change and write down any thing .. it fast and typo free

to the ones who still wondering how can this be used to speed up our things ... theres nothing .. let us say you have started all of the routers and want some
good aliases just copy and paste directly the initial configs section .. everytime it stops at hostname so that you can configure :whew ingenious :lol:


[code]#lab 4 eigrp loadbalancing#

---------------------------------------
initial config
--------------------------------------


en
config t
line con 0
logg sync
no exec-timeout
no ip domain-lookup
alias exec siib show ip int brief | i up
alias exec sir show ip route
hostname


-----------------------------------------
r1
-----------------------------------------

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut

-----------------------------------------
r2
----------------------------------------

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut

-----------------------------------------
r3
----------------------------------------
int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut

----------------------------------------
r4
----------------------------------------

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut


------------------------------------------
r5
------------------------------------------

int
ip addr 255.255.255.0
no shut

int
ip addr 255.255.255.0
no shut


------------------------------------------
fr configs
----------------------------------------

encap frame
frame map ip broad


encap frame
frame map ip broad


encap frame
frame map ip broad


encap frame
frame map ip broad[/code]

Summaraisation and Advanced Summaraisation - lab 3  

done with lab 3 summaraisation and advanced summaraisation

as always everything is cool and new point / concept "leak map"

Configuring leak-map option allows us to advertise a component route (one or more specific networks of a summary route) that would otherwise be
suppressed by the manual summaraisation .

Three rules :

If the leak-map is configured to reference a route-map that does not exist, only the summary route is advertised and the more specific routes are
suppressed

If the leak-map is configured to reference a route-map and the route-map is referencing an access-list that does not exist , then the summary routes and all
the specific routes are advertised

If the leakmap is configured to reference a route-map and the route-map matches and acl , all the permitted networks b the acl will be advertised along with
the summary route




for example we have

CODE
working

2.2.4.2
2.2.5.2
2.2.6.2
2.2.7.2


number 128 64 32 16 8 4 2 1

4 0 0 0 0 0 1 0 0
5 0 0 0 0 0 1 0 1
6 0 0 0 0 0 1 1 0
7 0 0 0 0 0 1 1 1

2.2.4.0/(8+8+6)

2.2.4.0/22

2.2.4.0 255.255.252.0


we have a summary address 2.2.4.0/22

1. int fa0/0
ip summa eigrp 100 2.2.4.0 255.255.252.0 leak-map rakesh---------------------> (rakesh is the name of the route-map which is not configured)

in this case only summary route is advertised which will be equal to the commands output "ip summa eigrp 100 2.2.4.0 255.255.252.0"

2.

route-map rakesh permit 10
match ip address 77(----------------> acl is not configured)
int fa0/0
ip summa eigrp 100 2.2.4.0 255.255.252.0 leak-map rakesh---------------------> (rakesh is the name of the route-map which has no access-list)

in this case all of the specific and summary routes are advertised i,e

2.2.4.0
2.2.4.0
2.2.5.0
2.2.6.0
2.2.7.0

3.

both acl and route-map are configured

access 66 permit 2.2.6.0 0.0.0.255
route-map rakesh permit 10
match ip address 66

int fa0/0
ip summ eigrp 100 2.2.4.0 255.255.252.0 leak rakesh

this would advertise summary address and address we wanted to permit/ deny in the acl .. look there is an implicit deny which is followed

this is what that i found interesting ...

i need more clear understanding !!! in what sense ? well iam not happy with the output .. first of all what is the use of leak-map .. next ok that is general sense of the question ... but it is behaving differently for different set of rules .. how does it allow / deny packets or how does it work ... so on ...? iam gonna post this question and will let you know




guday

Done with the lab 2  

Sunday, January 4, 2009

done with the lab 2 .. though sounded like a simple redistribution it was hard .. how is that hard ?

question was to redistribute eigrp and rip mutually .. at first it was good and ok i had done it and now the question demanded that rip should see the exact
hop count .. like if the network is 2 hops away it should see it as 120/2 likewise ..

at first i dint pay much attention and went on and redistributed

router rip
version 2
redist eigrp 100 metric 4


but this replaced all routes which are redistributed into rip with hop count of 4 ...

the solution was to create an access-list first and allow networks that were to be redistributed and then go ahead and create a route map which matched the
acl and set the metric to the respective hop count ..

after writing the acl again back to router menu and redist with the proper route-map

ppppoffffff

was difficult for me


on to lab 3

Notepad discovery haha  

CODE
en
conf t
line con 0
logg sync
no exec-timeout
no ip domain-lookup
alias exec siib show ip int brief | i up
alias exec sir show ip route
hostname


r1

int s0/0
ip addr 10.1.12.1 255.255.255.0
no shut

int l0
ip addr 1.1.1.1 255.0.0.0

r2

int s0/0
ip addr 10.1.12.2 255.255.255.0
no shut


int l0
ip addr 2.2.2.2 255.0.0.0

int fa0/0
ip addr 10.1.23.2 255.255.255.0
no shut


r3

int s0/0
ip addr 10.1.34.3 255.255.255.0
no shut


int fa0/0
ip addr 10.1.23.3 255.255.255.0
no shut


int l0
ip addr 3.3.3.3 255.0.0.0

r4

int s0/0
ip addr 10.1.34.4 255.255.255.0
no shut


int l0
ip addr 4.4.4.4 255.0.0.0



frame-relay

r1

int s0/0
encap frame
frame lmi-type cisco
frame map ip 10.1.12.2 102 broad
frame map ip 10.1.12.1 102

r2


int s0/0
encap frame
frame lmi-type cisco
frame map ip 10.1.12.1 201 broad
frame map ip 10.1.12.2 201

r3



int s0/0
encap frame
frame lmi-type cisco
frame map ip 10.1.34.4 304 broad
frame map ip 10.1.34.3 304

r4



int s0/0
encap frame
frame lmi-type cisco
frame map ip 10.1.34.3 403 broad
frame map ip 10.1.34.4 403


frs

frame-switch

frame switch
int s0/0
encap frame
frame lmi-type cisco
frame intf-type dce
frame route 102 interface serial 0/1 201
no shut


int s0/1
encap frame
frame lmi-type cisco
frame intf-type dce
frame route 201 interface serial 0/0 102
no shut


frs1

frame switch
int s0/0
encap frame
frame lmi-type cisco
frame intf-type dce
frame route 304 interface serial 0/1 403
no shut


int s0/1
encap frame
frame lmi-type cisco
frame intf-type dce
frame route 403 interface serial 0/0 304
no shut



surprised with the above config posted .. well sort of .. as i have already stated i was going on with narbiks wb and by mistake erased the config thinking that they would be of no use .. when i happened to visit the lab 2 i found that that lab was a continuation .. lesson learnt ... so left that lab thinking of writing down again the configs which nearly took 30 minutes for lab 1

this was the case with morning .. gave gap went an slept and on it again .. thinking of configs

and then i got the idea of note pad ... i know that after writing a config in router we can go for show run and copy paste blah blah and blah ..

that is a sort of time taking process ... 30 min config took me only 5 min to make ... this is what i followed ...

for cisco routers as we know we can copy and paste configs irrespective of prompts position ..

so i quickly created a config and wrote it in note pad ..(you need familiarity of course)

then went to interface mode

int s0/0
ip addr 255.255.255.0
no shut

copy this as many interfaces you have and just insert of change to your convinience

let us say i took that



r1

int s0/0
ip addr 255.255.255.0
no shut

int s0/1
ip addr 255.255.255.0
no shut

int s0/2
ip addr 255.255.255.0
no shut


after copy pasting three time change it to your will and frame - relay was hell lot easier in doing now .. i know many experts out there will have better tricks than this but who knows people who come and visit this may discover or find it helpful as i have done it now ..

i can 100% tell you this method is 10 times faster and 50% typos (ip address stuff) free

try it


regards
Rakesh

Vol 1  

After completing ie vol 1 as said i went after netmetric ccnp lab guide and it was swiftly done no complications . simple and straight foreward with minimal of 2 routers and max of 3 routers .. it has a total of 10 labs and all of them are childish neverthelss i could see some stub and redist configs

these are the labs and my experience

lab 1 - basic eigrp config -- childs play

lab 2 - configuring ip default-network command - some what confused but was silly wink.gif

lab 3 - route summaraisation in eigrp - straight foreward

lab 4 - loadbalancing accross equal paths - nothing great just set up eigrp and verify with trace route

lab 5 - loadbalanching accross unequal paths - nothing special from lab 4 change bandwidths and then use variance command beating around the bush

lab 6 - eigrp authentciation - simple i changed the topo i have included a redundant link and configured one link for md5 and other with no auth - it was fun

lab 7 - configuring eigrp stub - seen all of the varities -- at first felt a bit lost but when seen closely it was nothing




lab 8 - redistribute eigrp with rip v2 -- donot forget seed metric

lab 9 - redistribute eigrp with ospf -- simple include metric and subnets

lab 10 - redistribute connected - name says it all


so was fun with these ten labs going after netmetric ccie lab guide and will let you know .. i would advice any one to take a look at the netmetric first they are simple and boosts some confidence laugh.gif


regards
Rakesh

#SET TAG IE VOL 4.10#  

Saturday, January 3, 2009

#SET TAG IE VOL 4.10#

SET TAG:

-> To set a tag value of the destination routing protocol ,
use the set tag command in route-map config mode


USAGE GUIDELINES:

-> Use the route-map global config mode , and the match and
set route-map config commands , to define the conditions
for redistributing routes from one routing protocol into
another .

-> Each route-map command has a list of match and set commands
associated with it . The match commands specify the match
value - the conditions under which redistribution is
allowed for the current route-map command

-> The set commands specify the set actions - the particular
redistribution actions to perform if the criteria enforced
by the match commands are met .

-> The set route-map config commands specify the redistribution
set actions to be performed when all the match criteria
of a route map are met . When all match criteria are met,
all set actions are performed

#IP DEFAULT-NETWORK IE VOL 1 1/3/2009 1:27 PM #  

#IP DEFAULT-NETWORK IE VOL 1 1/3/2009 1:27 PM #

ip default-network:

-> To select a network as a candidate route for
computing the gateway of last resort , use the
"ip default-network" command in global config mode

USAGE GUIDELINES:

-> The cisco ios software uses both ad and metirc info to
determine the default route. multiple ip default-network
commands can be given.

-> All candidate default routes , both static (flagged by
ip default network command ) and dynamic , appear in the
routing table preceeded by asterisk

-> If the ip routing table indicates that the specified network
number is subnetted and a non zero subnet number is specified
,then the system will automatically config a static summ route

-> The static summary route is configured instead of a default
network . The effect of the static summary route is to
cause traffic destined for subnets that are not explicitly
listed in IP routing table to be routed using the
specified subnet

#DISTRIBUTE LIST 1/3/2009 1:34 PM#  

#DISTRIBUTE LIST 1/3/2009 1:34 PM#


distribute-list in:

-> To filter networks recieved in updates , use the "distribute-lists in"
commnad in appropriate config mode .


USAGE GUIDELINES:

-> This command must specify either an access list or a map-tag name of a route-map
The route-map is supported for OSPF and EIGRP

-> ospf routes cannot be filetered from entering the ospf db . if you use this
command for ospf, it only filters routes from the routing table , it does not
prevent link-state packets from being propogated




distribute-list out :

-> To suppress networks from being advertised in updates, use the "distribute-list out"
command in the appropriate configuration mode .

-> When networks are redistributed , a routing process name can be specified as an
optional trailing argument to the distribute-list command

-> Specifying this option causes the access list to be applied to only those
routes derived from the specified routing process

-> After the process-specific access list is applied, any access-list specified
by a distribute-list commnad without a process name argument will be applied

-> Addresses not specified in the distribute-list command will not be advertised
commnad will not be advertised in outgoing routing updates .

#DISTANCE EIGRP IE VOL 4.10 VOL 1 #  

#DISTANCE EIGRP IE VOL 4.10 VOL 1 #

DISTANCE EIGRP

-> To allow the use of two administrative distances
internal and external that could be a better route
to the node , use the "distance eigrp" command in
router config mode

INTERNAL DISTANCE :

-> Administrative distance for EIGRP internal routes .
internal routes are those that are learned from
another entity with the same as .


-> The distance can be a value from 1 to 255 . the
default ad for EIGRP INTERNAL ROUTES is 90


EXTERNAL DISTANCE :

-> Administrative distance for EIGRP external routes.
external routes are those for which the best path
is learned from a neighbor external to the as .

-> The distance can be a value from 1 to 255. The
default ad for EIGRP external routes is 170

USAGE GUIDELINES :

-> An administrative distance is a rating of the trustworthiness
of a routing information source, such as an induvidual
router or a group of routers .

-> Numerically , an ad is an interger from 0 to 255 . In
general , the higher the value , the lower the trust
rating . An ad of 255 means the routing info source cannot
be trusted at all should be ignored


-> use the "distance eigrp" command if another protocol is
known to be able to provide a better route to a node than
was actually learned via external EIGRP . or if some
internal routes should really be preffered by EIGRP

Configuration with and without leak map  

configuration with and without leak map :

the topology is not represented but the idea is to advertise our route along with the default summary address

here are the routing table and topology table entries of my topology

note 155.0.5.0/24 is the network of interest

CODE
before the leakmap application

r4#sir
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 155.0.0.5 to network 0.0.0.0

155.0.0.0/24 is subnetted, 3 subnets
C 155.0.0.0 is directly connected, Serial0/0
C 155.0.4.0 is directly connected, Loopback0
C 155.0.45.0 is directly connected, Serial0/1
D* 0.0.0.0/0 [90/10639872] via 155.0.0.5, 00:28:07, Serial0/0
r4#show ip eigrp topo
IP-EIGRP Topology Table for AS(100)/ID(155.0.4.4)

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

P 0.0.0.0/0, 1 successors, FD is 10639872
via 155.0.0.5 (10639872/128256), Serial0/0
via 155.0.45.5 (40640000/128256), Serial0/1
P 155.0.0.0/24, 1 successors, FD is 10511872
via Connected, Serial0/0
P 155.0.4.0/24, 1 successors, FD is 128256
via Connected, Loopback0
P 155.0.45.0/24, 1 successors, FD is 40512000
via Connected, Serial0/1
r4#


CODE
After the leak map application

r4#sir
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 155.0.0.5 to network 0.0.0.0

155.0.0.0/24 is subnetted, 4 subnets
C 155.0.0.0 is directly connected, Serial0/0
D 155.0.5.0 [90/10639872] via 155.0.0.5, 00:07:49, Serial0/0--------------------------------->
C 155.0.4.0 is directly connected, Loopback0
C 155.0.45.0 is directly connected, Serial0/1
D* 0.0.0.0/0 [90/10639872] via 155.0.0.5, 00:26:00, Serial0/0
r4#show ip eigrp topo
IP-EIGRP Topology Table for AS(100)/ID(155.0.4.4)

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

P 0.0.0.0/0, 1 successors, FD is 10639872
via 155.0.0.5 (10639872/128256), Serial0/0
via 155.0.45.5 (40640000/128256), Serial0/1
P 155.0.0.0/24, 1 successors, FD is 10511872
via Connected, Serial0/0
P 155.0.5.0/24, 1 successors, FD is 10639872--------------------------->
via 155.0.0.5 (10639872/128256), Serial0/0
via 155.0.45.5 (40640000/128256), Serial0/1
P 155.0.4.0/24, 1 successors, FD is 128256
via Connected, Loopback0
P 155.0.45.0/24, 1 successors, FD is 40512000
via Connected, Serial0/1
r4#

#IP SUMMARY-ADDRESS EIGRP FRI JAN 2 2K9 #  

#IP SUMMARY-ADDRESS EIGRP FRI JAN 2 2K9 #

TO CONFIGURE A SUMMARY AGGREGATE ADDRESS FOR A SPECIFIED
INTERFACE, USE THE "ip summary-address eigrp" command
in interface configuration mode .


"ip summary-address eigrp as-number ip-addr [admin][leakmap]"



USAGE GUIDELINES

The "ip summary-address eigrp" command is used to configure
interface level eigrp summaraisation.

EIGRP summary routes are given an administrative distance
value of 5. The administrative distance metric is used
to advertise a summary without installing it in the
routing table

By default, EIGRP summaries subnet routes to the network
level.The "no auto" command can be entered to configure
subnet level summaraisation

EIGRP SUPPORT FOR LEAKING ROUTES :

Configuring the leak-map keyword allows to advertise a
component route that would otherwise be suppressed by the
manual summary.

Any component subset of the summary can be leaked . A route
map and access list must be defined to source the leaked
route

The following is the default behaviour if an incomplete
cnfg is entered .

A) If the leak-map keyword is configured to reference a
non existant routemap, the configuration key word has no
effect. The summary address is advertised but all
component routes are suppressed

cool.gif If the leak-map keyword is configured but the access-list
does not exist or the route map does not reference the
access list , the summary address and component routes
are sent .

#IE EIGRP STUB JAN 1 2K9#  

Thursday, January 1, 2009

going on to single technologies for the preciseness and also referring doc cd and making some kinda of notes . netmasterss igp is helping on the way .. any ways doing some of the ethreal videos and laura chappels tcp/ip video as to have some base level packet understanding .. it will take time though but worth spending .. i was advised to have some real good grip on tcp/ip packet understanding by my very good frnd talentpk ... anyways i had done a scenario on ie eigrp stub ..




#IE EIGRP STUB JAN 1 2K9#

EIGRP STUB:

To configure a router as a stub using EIGRP , use the
"eigrp stub" command in router config mode

"eigrp stub [recieve-only connected static summary redist]"

recieve only - sets the router as a recieve-only neigh

connected - advertises connected routes

static - advertise static route

summary - advertises summary routes

redistributed - advertises redistributed routes from other
and autonomous systems

USAGE GUIDELINES:

Use the "eigrp stub" command to configure as a stub where
the router directs all IP traffic to a distribution router

The "eigrp stub" command can be modified with serveral options
and these options can be used in any combination except
receive-only keyword

The receive-only keyword will restrict the router from sharing
any of its routes with any router in that EIGRP as, as the
receive-only keyword will not permit any other option to
be specified because it prevents any type of route from
being sent

The four other optional keywords (connected , static ,
summary, and redistributed) can be used in any combination
but cannot be used with the receive-only keyword)

The connected keyword permits the EIGRP stub routing feature
to send connected routes.if the connected routes are not
covered by a network command statement , it may be
necessary to redistribute connected routes with
redistribute connected command under EIGRP process . This
option is enabled by default

The "static" keyword permits the EIGRP stub routing feature
to send traffic to send static routes.without the configuration
of this option, EIGRP will not send any static routes,
including internal static routes that normally would be
automatically redistributed . it will still be necessary
to redistribute static routes with redistribute static command

The summary keyword permits the EIGRP stub routing feature
to send summary routes . summary routes can be created
manually with summary address command or automatically at a
major network border router with no auto command enabled

The redistributed keyword permits the EIGRP stub routing
feature to send other routing protocols and autonomous
systems .

Multiaccess interfaces , frame-relay are supported by the
EIGRP stub routing feature only when all routers on that,
interface, except the hub, are configured as stub routers.

Design by Blogger Buster | Distributed by Blogging Tips