From: xander (xander@xxxxxx)
Date: Thu Apr 12 2001 - 15:25:33 GMT-3
Hello Robert,
As in one movie someone said "Shit's happend" :-)
Ahhh... Yeah! "Forest Gump" (don't remember the spelling)
So we pride Cisco that they will not involve "real-life" faults in T/S
section of CCIE lab :-)))
MR> Here is a scenario which caught me out BIG time in a real life situation
MR> using ISIS.
MR> To make it easier
MR> Router A has a serial connection to Router B
MR> Everything is up layer 1 & 2i.e CDP can indeed see Router B if you are on
MR> Router A and vice versa. Router B can't see any routes from Router A or
MR> beyond.
MR> NOW Routers A serial 0's ip address is 172.16.130.5, Routers B serial 0's
MR> ip address is 172.16.130.5.
MR> Spot the deliberate mistake.
MR> Although you say AHA he has the same ip address on the serial connections.
MR> SO, quite rightly ISIS says, go away I will never make an adjacency with
MR> myself !!!! :-(
MR> However, it took me quite a while to discover that these IP addresses were
MR> indeed duplicated.
MR> REASON or should I make it a question? I think question would be better.
MR> Q: What do you think would happen if I was on Router A and telnetted to
MR> 172.16.130.5, would I telnet to Router A or B. :->
MR> A: This is why it took me a while to realise this. I started debugging
MR> adjacencies, blaming a new controller card which was the first time I had
MR> used this in ISIS, everything bar the easy problem. Mental Note for me her
e
MR> is don't dive in head first, always fault find the layers and remember this
MR> fault because it is nasty!!!! :-<
MR> What made it worse was the customer sitting over my shoulder saying WHY
MR> isn't this working, I knew we shouldn't have bought those new fangled route
r
MR> things!!!!!
MR> Oh the joys of life!!!!
-- WBW, xander mailto:xander@adt.ru CCNA, CCNP+VoiceAccess, CCIE first attempt in Brussels 19-20, April, 2001...
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:45 GMT-3