From: kumara.shunmugam@wipro.com
Date: Thu Aug 04 2005 - 02:45:13 GMT-3
It is not only DIS need a direct connectivity with all the peers.This rule can be satisfied by making R3 as a DIS(HUB) in this topology. What I found in L2 update is, ISIS(L2) will not advertise a route to another neighbor thru the same interface from it learned that route.. Yes, if you look at this diagram R6 also has a L2 peering with R3 thru Ethernet and R3 advertise the routes learned from R6 to R1 thru frame-relay even through these guys do not have any L2 direct connectivity at this point of time. (becoz I had shutdown the R1 ethernet & P2P serial to R3). Where as the R5 routes are not going to R1 or vice-versa
Regards
Shunmugam
-----Original Message-----
From: Loc Pham [mailto:loc.pham@comcast.net]
Sent: Wednesday, August 03, 2005 10:29 AM
To: Kumara Guru Shunmugam L (WI01 - Services); manoj.kumar@citigroup.com; ccielab@groupstudy.com
Subject: RE: IWEB Lab 14 Task 5.11 IS-IS in HUB-n-SPOKE
Kumara,
You have the SG handy, right ? the Brians explaint it what you just prove ... The DIS need to have direct layer-2 circuit or ISIS-da will not syncronize,
GRE, add subnet or bust ;)
lP.
> This is happening if I shutdown all other links in R1 except Frame-relay
> connection Serial0. Is it calling the same old Split-horizon funda like one in
> Distance vector protocols ?(even though this is not exists in ISIS). The most
> fun is when other interfaces at R1 are up, then the routes are also learned thru
> frame-relay link and installing in to the routing table as a same metric path
> along with other links. But when we shutdown other interfaces except frame-relay
> in R1, it totally stops communicating (even with Hub also(R3) and not learning
> any thing over FR interface.(Which network theory is Appling here ??
>
>
>
>
>
> -----Original Message-----
> From: Kumar, Manoj [mailto:manoj.kumar@citigroup.com]
> Sent: Wednesday, August 03, 2005 7:56 AM
> To: Kumara Guru Shunmugam L (WI01 - Services); ccielab@groupstudy.com
> Subject: RE: IWEB Lab 14 Task 5.11 IS-IS in HUB-n-SPOKE
>
> Did you try shutting down the other links between R3 and R1 (if I remember
> correctly, this setup has multiple connections between R1 and R3, ethernet, FR
> and p2p) you will find that R1 isis database will stop synchronizing with that
> R5 and R5 will not see any routes from R1.
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> kumara.shunmugam@wipro.com
> Sent: Wednesday, August 03, 2005 5:43 PM
> To: ccielab@groupstudy.com
> Subject: IWEB Lab 14 Task 5.11 IS-IS in HUB-n-SPOKE
>
>
> Hi all
> There was a requirement in the lab to establish L2 neighbor-ship between
> R1,R3,R5 , where R3 is HUB for both other routers. As per the Solution ISIS
> will not work properly on hub-spoke technology due to its lack of network type
> availability (isis network command) .The solution was to create GRE tunnel
> between these thee (R3 to R1 & R3 to R5). But I am wondering , without doing
> this , the neighbor-ship got estabilished for me and routes are also properly
> advertising with proper next-hop IP. DIS selection was also very smooth .. I
> think there should be some hidden issue which might popup later if I continue
> to use this setup.. Can anyone tell me what could be the reason..
>
> R3 -Config
>
> interface Serial1/0
> ip address 167.1.135.3 255.255.255.0
> ip router isis
> encapsulation frame-relay
> serial restart_delay 0
> frame-relay map clns 301 broadcast
> frame-relay map clns 305 broadcast
> frame-relay map ip 167.1.135.1 301 broadcast
> frame-relay map ip 167.1.135.5 305 broadcast
>
> router isis
> net 00.3490.0001.0001.0003.00
> is-type level-2-only
>
> R3#show clns is-neighbors
> System Id Interface State Type Priority Circuit Id Format
> R1 Se1/0 Up L2 64 R5.02 Phase V
> R5 Se1/0 Up L2 64 R5.02 Phase V
> R3#show clns neighbors
>
> System Id Interface SNPA State Holdtime Type Protocol
> R1 Se1/0 DLCI 301 Up 26 L2 IS-IS
> R5 Se1/0 DLCI 305 Up 8 L2 IS-IS
>
> Gateway of last resort is not set
>
> C 204.12.1.0/24 is directly connected, FastEthernet0/0
> 167.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
> C 167.1.135.0/24 is directly connected, Serial1/0
> C 167.1.34.0/24 is directly connected, Serial1/1.34
> i L2 167.1.45.0/27 [115/20] via 167.1.135.5, Serial1/0
> C 167.1.13.0/24 is directly connected, Serial1/2
> 150.1.0.0/24 is subnetted, 5 subnets
> i L2 150.1.6.0 [115/20] via 204.12.1.6, FastEthernet0/0
> i L2 150.1.5.0 [115/20] via 167.1.135.5, Serial1/0
> i L2 150.1.4.0 [115/20] via 167.1.34.4, Serial1/1.34
> C 150.1.3.0 is directly connected, Loopback0
> i L2 150.1.1.0 [115/20] via 167.1.13.1, Serial1/2
> [115/20] via 204.12.1.1, FastEthernet0/0
> [115/20] via 167.1.135.1, Serial1/0
>
>
>
> R5-Config
> interface Serial0/0
> ip address 167.1.135.5 255.255.255.0
> ip router isis
> encapsulation frame-relay
> frame-relay map clns 503 broadcast
> frame-relay map ip 167.1.135.1 503
> frame-relay map ip 167.1.135.3 503 broadcast
> no frame-relay inverse-arp
>
> router isis
> net 00.3490.0001.0001.0005.00
> is-type level-2-only
>
> R5# show clns neighbors
> System Id Interface SNPA State Holdtime Type Protocol
> R3 Se0/0 DLCI 503 Up 24 L2 IS-IS
>
> R5# show clns is-neighbors
> System Id Interface State Type Priority Circuit Id Format
> R3 Se0/0 Up L2 64 R5.02 Phase V
> R5#
>
>
> R5#Show ip route
> Gateway of last resort is not set
>
> i L2 204.12.1.0/24 [115/20] via 167.1.135.3, Serial0/0
> 167.1.0.0/16 is variably subnetted, 6 subnets, 2 masks
> C 167.1.135.0/24 is directly connected, Serial0/0
> i L2 167.1.34.0/24 [115/20] via 167.1.135.3, Serial0/0
> C 167.1.45.0/27 is directly connected, BRI0/0
> C 167.1.58.0/24 is directly connected, FastEthernet1/0
> C 167.1.5.0/24 is directly connected, Ethernet0/0
> i L2 167.1.13.0/24 [115/20] via 167.1.135.3, Serial0/0
> 150.1.0.0/24 is subnetted, 5 subnets
> i L2 150.1.6.0 [115/30] via 167.1.135.3, Serial0/0
> C 150.1.5.0 is directly connected, Loopback0
> i L2 150.1.4.0 [115/30] via 167.1.135.3, Serial0/0
> i L2 150.1.3.0 [115/20] via 167.1.135.3, Serial0/0
> i L2 150.1.1.0 [115/30] via 167.1.135.3, Serial0/0
> R5#ping 150.1.1.1
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 150.1.1.1, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 88/89/92 ms
> R5#
>
> R1-Config
>
> interface Serial0
> ip address 167.1.135.1 255.255.255.0
> ip router isis
> encapsulation frame-relay
> clockrate 64000
> frame-relay map clns 103 broadcast
> frame-relay map ip 167.1.135.3 103 broadcast
> frame-relay map ip 167.1.135.5 103
> no frame-relay inverse-arp
>
> router isis
> net 00.3490.0001.0001.0001.00
> is-type level-2-only
>
> System Id Interface SNPA State Holdtime Type Protocol
> R3 Se0 DLCI 103 Up 27 L2
> IS-IS
> R3 Et0 000d.bc16.61e0 Up 7 L2
> IS-IS
> R6 Et0 0008.21f0.2e30 Up 29 L2
> IS-IS
> R3 Se1 *HDLC* Up 29 L2
> IS-IS
> R1#show clns is-neighbors
>
> System Id Interface State Type Priority Circuit Id Format
> R3 Se0 Up L2 64 R5.02 Phase
> V
> R3 Et0 Up L2 64 R3.01
> Phase V
> R6 Et0 Up L2 64 R3.01
> Phase V
> R3 Se1 Up L2 0 00
> Phase V
>
> Gateway of last resort is not set
>
> C 204.12.1.0/24 is directly connected, Ethernet0
> 167.1.0.0/16 is variably subnetted, 4 subnets, 2 masks
> C 167.1.135.0/24 is directly connected, Serial0
> i L2 167.1.34.0/24 [115/20] via 204.12.1.3, Ethernet0
> [115/20] via 167.1.13.3, Serial1
> [115/20] via 167.1.135.3, Serial0
> i L2 167.1.45.0/27 [115/30] via 167.1.135.3, Serial0
> [115/30] via 204.12.1.3, Ethernet0
> [115/30] via 167.1.13.3, Serial1
> C 167.1.13.0/24 is directly connected, Serial1
> 150.1.0.0/24 is subnetted, 5 subnets
> i L2 150.1.6.0 [115/20] via 204.12.1.6, Ethernet0
> i L2 150.1.5.0 [115/30] via 167.1.135.3, Serial0
> [115/30] via 204.12.1.3, Ethernet0
> [115/30] via 167.1.13.3, Serial1
> i L2 150.1.4.0 [115/30] via 204.12.1.3, Ethernet0
> [115/30] via 167.1.13.3, Serial1
> [115/30] via 167.1.135.3, Serial0
> i L2 150.1.3.0 [115/20] via 204.12.1.3, Ethernet0
> [115/20] via 167.1.13.3, Serial1
> [115/20] via 167.1.135.3, Serial0
> C 150.1.1.0 is directly connected, Loopback0
> R1#ping 150.1.5.5
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 150.1.5.5, timeout is 2 seconds:
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 56/112/269 ms
> R1#
>
>
>
>
>
>
>
> Confidentiality Notice
>
> The information contained in this electronic message and any attachments to
> this message are intended
> for the exclusive use of the addressee(s) and may contain confidential or
> privileged information. If
> you are not the intended recipient, please notify the sender at Wipro or
> Mailadmin@wipro.com immediately
> and destroy all copies of this message and any attachments.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
> Confidentiality Notice
>
> The information contained in this electronic message and any attachments to this
> message are intended
> for the exclusive use of the addressee(s) and may contain confidential or
> privileged information. If
> you are not the intended recipient, please notify the sender at Wipro or
> Mailadmin@wipro.com immediately
> and destroy all copies of this message and any attachments.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Confidentiality Notice
The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or Mailadmin@wipro.com immediately
and destroy all copies of this message and any attachments.
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:18 GMT-3