From: backbone systems (backbone.systems@gmail.com)
Date: Sat Mar 21 2009 - 11:19:07 ART
hmmm ......for me its L1L2....R1------R3 connected over ISIS
R1(config-if)#do sh isis ne
System Id Type Interface IP Address State Holdtime Circuit Id
R3 L1 Se2/0 150.0.0.3 UP 26 R1.01
R3 L2 Se2/0 150.0.0.3 UP 21 R1.01
R1(config-if)#do sh clns ne
System Id Interface SNPA State Holdtime Type Protocol
R3 Se2/0 DLCI 103 Up 28 L1L2 IS-IS
R3(config-if)#do sh isis ne
System Id Type Interface IP Address State Holdtime Circuit Id
R1 L1 Se2/0 150.0.0.1 UP 7 R1.01
R1 L2 Se2/0 150.0.0.1 UP 7 R1.01
R3(config-if)#do sh clns ne
System Id Interface SNPA State Holdtime Type Protocol
R1 Se2/0 DLCI 301 Up 8 L1L2 IS-IS
R3(config-if)#
interface Serial2/0
ip address 150.0.0.3 255.0.0.0
ip router isis
encapsulation frame-relay
serial restart-delay 0
frame-relay map clns 301 broadcast
frame-relay map ip 150.0.0.1 301 broadcast
no frame-relay inverse-arp
end
On Sat, Mar 21, 2009 at 1:52 PM, vignesh sethuraman
<sethuvignesh@yahoo.co.in> wrote:
> Hello Experts,
>
> When is-is adjacency is formed between routers which are connected via ATM or
> Ethernet, they form by default L1/L2 adjacency, but when the routers are
> connected via frame-relay, they form L2 adjacency by default.
>
> I don't have any issues with the connectivity. If i ping from R1 loopback to
> R5 loopback, its working fine, but when the routers are connected via
> frame-relay, they form L2 adjacency by default instead of L1/L2 adjacency.
>
> Here is my Scenario and Configs
>
> R1 -- ATMSW--- R2---ethernet----R4 ----FRSW---R5
>
> R1:
> Rack1R1#sh run | b 4/0
> interface ATM4/0
> description Put ATM PVC Configs Here
> ip address 150.1.12.1 255.255.255.0
> ip router isis
> no atm enable-ilmi-trap
> pvc 0/102
> protocol ip 150.1.12.2 broadcast
> protocol clns 49.0024.0000.0000.0002.00 broadcast
> !
> interface Loopback0
> ip address 150.1.1.1 255.255.255.0
> ip router isis
> end
> !
> router isis
> net 49.0001.0000.0001.00
>
> Rack1R1#sh clns is-neighbors
> System Id Interface State Type Priority Circuit Id Format
> Rack1R2 AT4/0 Up L2 64 Rack1R1.01 Phase V
>
> R2:
>
> Rack1R2#sh run | b 4/0
> interface FastEthernet0/0
> ip address 150.1.24.2 255.255.255.0
> ip router isis
> duplex half
> isis circuit-type level-2-only
> !
> interface ATM4/0
> ip address 150.1.12.2 255.255.255.0
> ip router isis
> no atm enable-ilmi-trap
> pvc 0/201
> protocol clns 49.0001.0000.0001.00 broadcast
> protocol ip 150.1.12.1 broadcast
> !
> interface Loopback0
> ip address 150.1.2.2 255.255.255.0
> ip router isis
> !
> interface Loopback1
> ip address 150.1.22.2 255.255.255.0
> ip router isis
> end
> !
> router isis
> net 49.0024.0000.0000.0002.00
>
> Rack1R2#sh clns is-neighbors
>
> System Id Interface State Type Priority Circuit Id Format
> Rack1R4 Fa0/0 Up L2 64 Rack1R4.01 Phase V
> Rack1R1 AT4/0 Up L1L2 128/64 Rack1R1.01 Phase V
>
> R4:
>
> Rack1R4#sh run | b 0/0
> interface Ethernet0/0
> ip address 150.1.24.4 255.255.255.0
> ip router isis
> half-duplex
> isis circuit-type level-2-only
> !
> interface Serial1/0
> ip address 150.1.45.4 255.255.255.0
> ip router isis
> encapsulation frame-relay
> serial restart-delay 0
> frame-relay map ip 150.1.45.5 405 broadcast
> frame-relay map clns 405 broadcast
> no frame-relay inverse-arp
> !
> interface Loopback0
> ip address 150.1.4.4 255.255.255.0
> ip router isis
> end
> !
> interface Loopback1
> ip address 150.1.44.4 255.255.255.0
> ip router isis
> end
> !
> router isis
> net 49.0024.0000.0000.0004.00
>
> Rack1R4#sh clns is-neighbors
> System Id Interface State Type Priority Circuit Id Format
> Rack1R5 Se1/0 Up L2 64 Rack1R5.01 Phase V
> Rack1R2 Et0/0 Up L2 64 Rack1R4.01 Phase V
>
> R5:
> !
> interface Serial1/0
> ip address 150.1.45.5 255.255.255.0
> ip router isis
> encapsulation frame-relay
> serial restart-delay 0
> frame-relay map ip 150.1.45.4 504 broadcast
> frame-relay map clns 504 broadcast
> no frame-relay inverse-arp
> !
> interface Loopback0
> ip address 150.1.5.5 255.255.255.0
> ip router isis
> end
> !
> router isis
> net 49.0005.0000.0000.0005.00
> !
> Rack1R5#sh clns is-neighbors
>
> System Id Interface State Type Priority Circuit Id Format
> Rack1R4 Se1/0 Up L2 64 Rack1R5.01 Phase V
>
> To check connectivity, i used ping from R1 to R5, where 150.1.1.1 is R1's
> loopback and 150.1.5.5 is R5's loopback.
>
> Rack1R1#ping 150.1.5.5 source lo0
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 150.1.5.5, timeout is 2 seconds:
> Packet sent with a source address of 150.1.1.1
> !!!!!
> Success rate is 100 percent (5/5), round-trip min/avg/max = 604/636/740 ms
> Rack1R1#
>
> Could you please someone tell me if I am missing anything in my config.
>
> Thanks,
> Vignesh
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> From Chandigarh to Chennai - find friends all over India. Go to
> http://in.promos.yahoo.com/groups/citygroups/
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:06 ART