From: Carlos Alberto Trujillo Jimenez (carlos.trujillo.jimenez@gmail.com)
Date: Wed Mar 19 2008 - 21:38:12 ART
> Gangs, do you think it is related to IOS bug??? Or how to isolate any
> failure in FR?? I am afraid that the FRSW is responsible for that.
Addicted.
If you think is the frame-relay switch the originator of the problem, you
can see in the router the LAST TIME PVC STATUS CHANGED, like the following:
r1#show frame-relay pvc
PVC Statistics for interface Serial0/0/0 (Frame Relay DTE)
Active Inactive Deleted Static
Local 3 0 0 0
Switched 0 0 0 0
Unused 0 0 0 0
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE =
Serial0/0/0.123
input pkts 13614 output pkts 13650 in bytes 1624595
out bytes 1456580 dropped pkts 0 in pkts dropped
0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 9268 out bcast bytes 1148650
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
pvc create time 1d01h, *last time pvc status changed 1d01h*
*last time pvc status changed 1d01h*
2008/3/19, cisco-addicted <cisco.addicted@gmail.com>:
>
> Dears,
>
> Thnaks for your help, I tried & worked on all the comments and notes you
> provided but nothing happened.
>
>
>
> Dear Jonathan,
>
> I tried the troubleshooting chart and all the ping working fine with me
> from everywhere to everywhere with different packet size.
>
>
>
> Gangs, do you think it is related to IOS bug??? Or how to isolate any
> failure in FR?? I am afraid that the FRSW is responsible for that.
>
>
>
> Check the configuration in the R2 (the hub) and R1 & R2 the spokes and I
> am
> waiting for your feedback.
>
>
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R2
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
> !
>
> interface Serial0/2/0
>
> ip address 183.1.123.2 255.255.255.0
>
> encapsulation frame-relay
>
> no ip split-horizon eigrp 100
>
> clockrate 125000
>
> frame-relay map ip 183.1.123.1 201 broadcast
>
> frame-relay map ip 183.1.123.3 203 broadcast
>
> no frame-relay inverse-arp
>
> frame-relay lmi-type cisco
>
> !
>
> interface Serial0/2/1
>
> no ip address
>
> shutdown
>
> !
>
> router eigrp 100
>
> network 150.1.2.2 0.0.0.0
>
> network 183.1.28.2 0.0.0.0
>
> network 183.1.123.2 0.0.0.0
>
> no auto-summary
>
> eigrp router-id 150.1.2.2
>
> !
>
>
>
> Rack1R2#sh ip eigrp neighbors
>
> IP-EIGRP neighbors for process 100
>
> H Address Interface Hold Uptime SRTT
> RTO Q Seq
>
> (sec) (ms) Cnt
> Num
>
> 1 183.1.123.1 Se0/2/0 139 22:40:52
> 47 1140 0 43
>
>
>
>
>
>
>
>
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R1
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
>
>
>
>
> !
>
> interface Serial0/2/0
>
> ip address 183.1.123.1 255.255.255.0
>
> encapsulation frame-relay
>
> frame-relay map ip 183.1.123.3 102
>
> frame-relay map ip 183.1.123.2 102 broadcast
>
> no frame-relay inverse-arp
>
> frame-relay lmi-type cisco
>
> !
>
> interface Serial0/2/1
>
> no ip address
>
> shutdown
>
> !
>
> router eigrp 100
>
> network 150.1.1.1 0.0.0.0
>
> network 183.1.17.1 0.0.0.0
>
> network 183.1.123.1 0.0.0.0
>
> no auto-summary
>
> eigrp router-id 150.1.1.1
>
> !
>
> !
>
> Rack1R1#sh ip eigrp neighbors
>
> IP-EIGRP neighbors for process 100
>
> H Address Interface Hold Uptime SRTT
> RTO Q Seq
>
> (sec) (ms) Cnt
> Num
>
> 0 183.1.123.2 Se0/2/0 164
> 22:40:30 105 1140 0 34
>
>
>
>
>
>
>
>
>
>
>
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! R 3
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
>
>
>
>
>
> !
>
> interface Serial1/0
>
> ip address 183.1.123.3 255.255.255.0
>
> encapsulation frame-relay
>
> frame-relay map ip 183.1.123.1 302
>
> frame-relay map ip 183.1.123.2 302 broadcast
>
> no frame-relay inverse-arp
>
> !
>
>
>
> !
>
> router eigrp 100
>
> redistribute connected metric 10000 10 255 1 1500 route-map
> CONNECTED_INTERFACE
>
> network 183.1.123.3 0.0.0.0
>
> no auto-summary
>
> eigrp router-id 150.1.3.3
>
> !
>
> Rack1R3#sh ip ei neighbors
>
> IP-EIGRP neighbors for process 100
>
> H Address Interface Hold Uptime SRTT
> RTO Q Seq
>
> (sec) (ms) Cnt
> Num
>
> 0 183.1.123.2 Se1/0 163 22:46:02
> 56 1140 0 34
>
> Rack1R3#
>
>
>
>
>
>
>
>
>
> From: But Nicky [mailto:lyredhair@gmail.com]
> Sent: Tuesday, March 18, 2008 5:49 AM
> To: Rik Guyler
> Cc: Shine Joseph; Adel Karim; Envuladu Tsaku; steveaggie@gmail.com;
> cisco-addicted; Cisco certification
> Subject: Re: EIGRP adjacency Flapping
>
>
>
> Hi all,
> I think maybe there two causes:
> 1. split-horizon
> 2. duplicate router-id at EIGRP process.
>
> BR,
> But.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:54 ART