From: Sharma, Mohit (mohit.sharma@hp.com)
Date: Sat Jun 12 2004 - 14:31:46 GMT-3
Hi All,
While doing a lab for ISIS my routers have suddenly gone berserk.
I have this setup-
RTR3(7500)
multipoint - multipoint
/ \
/FR \FR
RTR4(2500) RTR5(2500)
Serial0 Serial0
Till the time IP was there everything was working fine, after I
configured ISIS, I cant ping even the spokes that are directly
connected. Strangely the clns adjacency is ON, also when I ping from
R3-R4 or R3-R5 I can see the packets coming back in the debug but ping
fails. Here are the configs-
**********************************************
Rack1R3#interface Serial3/0
no ip address
encapsulation frame-relay
serial restart-delay 0
clockrate 64000
no frame-relay inverse-arp
end
interface Serial3/0.53 multipoint
ip address 164.1.35.3 255.255.255.0
ip router isis
isis hello-multiplier 5
isis hello-interval 1
frame-relay map clns 305 broadcast
frame-relay map ip 164.1.35.3 305 broadcast
frame-relay map ip 164.1.35.5 305 broadcast
interface Serial3/0.43 multipoint
ip address 164.1.34.3 255.255.255.0
ip router isis
isis hello-multiplier 5
isis hello-interval 1
frame-relay map clns 304 broadcast
frame-relay map ip 164.1.34.3 304 broadcast
frame-relay map ip 164.1.34.4 304 broadcast
***********************************************
Rack1R4#
interface Serial0
ip address 164.1.34.4 255.255.255.0
ip router isis
encapsulation frame-relay
no fair-queue
frame-relay map clns 403 broadcast
frame-relay map ip 164.1.34.3 403 broadcast
frame-relay map ip 164.1.34.4 403 broadcast
no frame-relay inverse-arp
isis hello-multiplier 5
isis hello-interval 1
End
Rack1R4#sh fram map
Serial0 (up): CLNS dlci 403(0x193,0x6430), static,
broadcast,
CISCO, status defined, active
Serial0 (up): ip 164.1.34.3 dlci 403(0x193,0x6430), static,
broadcast,
CISCO, status defined, active
Serial0 (up): ip 164.1.34.4 dlci 403(0x193,0x6430), static,
broadcast,
CISCO, status defined, active
Rack1R4#sh clns nei
System Id Interface SNPA State Holdtime Type
Protocol
0001.0001.0003 Se0 DLCI 403 Up 4 L2
IS-IS
Rack1R4#ping 164.1.34.3
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 164.1.34.3, timeout is 2 seconds:
.
00:15:45: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4.
00:15:47: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4
00:15:48: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4..
00:15:50: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4.
Success rate is 0 percent (0/5)
Rack1R4#
00:16:02: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4
Rack1R4#
00:16:04: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.4
Rack1R4#
00:16:06: ICMP: echo reply rcvd, src 164.1.34.3, dst 164.1.34.
************************************************************************
The same is happening on R5. IP traffic over the FR cloud is not
"working" at all.
Could somebody please tell me what is happening here. I am going
BONKERS.
Many Thanks,
Mohit
P.S. I did rebooot all the routers also.
This archive was generated by hypermail 2.1.4 : Sat Jul 03 2004 - 19:40:39 GMT-3