From: Hunt Lee (ciscoforme3@yahoo.com.au)
Date: Thu Mar 27 2003 - 11:22:46 GMT-3
Hello Chris,
I have look for that already, but it doesn't look like that is the case...
RTA RTB
\ /
FrameA --- Async (Cisco console cable) --- FrameB
/ \
RTB RTD
frame_B#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Async1 10.1.9.6 YES NVRAM up up
Ethernet0 unassigned YES NVRAM administratively down down
Serial0 unassigned YES NVRAM up up
Serial1 unassigned YES NVRAM up up
Tunnel0 10.1.9.2 YES NVRAM up up
frame_B#sh run
frame_B#sh running-config int tu0
Building configuration...
Current configuration : 113 bytes
!
interface Tunnel0
ip address 10.1.9.2 255.255.255.252
tunnel source Async1
tunnel destination 10.1.9.5
end
frame_B#sh ip route 10.1.9.5
Routing entry for 10.1.9.5/32
Known via "connected", distance 0, metric 0 (connected, via interface)
Routing Descriptor Blocks:
* directly connected, via Async1
Route metric is 0, traffic share count is 1
frame_B#
N.B:- Even though the interface are all up, you can't ping it...
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.9.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
frame_B#
But if I admin shut and un-shut it... it will work for another while
frame_B#config t
Enter configuration commands, one per line. End with CNTL/Z.
frame_B(config)#int async 1
frame_B(config-if)#shut
frame_B(config-if)#exit
frame_B(config)#int tunnel 0
frame_B(config-if)#
*Mar 1 17:02:05.395 UTC: %LINK-5-CHANGED: Interface Async1, changed state to
administratively down
*Mar 1 17:02:06.395 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async1,
changed state to down
frame_B(config-if)#
*Mar 1 17:02:06.955 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0,
changed state to down
*Mar 1 17:02:08.503 UTC: %SYS-5-CONFIG_I: Configured from console by consolein ttu
frame_B(config)#in tunnel 0
frame_B(config-if)#shut
frame_B(config-if)#
frame_B#
*Mar 1 17:02:15.059 UTC: %SYS-5-CONFIG_I: Configured from console by console
*Mar 1 17:02:16.511 UTC: %LINK-5-CHANGED: Interface Tunnel0, changed state to
administratively down
config t
Enter configuration commands, one per line. End with CNTL/Z.
frame_B(config)#int async 1
frame_B(config-if)#no shut
frame_B(config-if)#exit
frame_B(config)#int tunnel 0
frame_B(config-if)#no shut
frame_B(config-if)#
frame_B#
*Mar 1 17:02:43.331 UTC: %LINK-3-UPDOWN: Interface Async1, changed state to down
*Mar 1 17:02:45.123 UTC: %SYS-5-CONFIG_I: Configured from console by console
*Mar 1 17:02:46.195 UTC: %LINK-3-UPDOWN: Interface Async1, changed state to up
*Mar 1 17:02:46.715 UTC: %LINK-3-UPDOWN: Interface Tunnel0, changed state to up
*Mar 1 17:02:48.419 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async1,
changed state to up 10.1.9.1
frame_B#ping 10.1.9.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.9.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 92/94/96 ms
frame_B#
* Mar 1 17:02:57.023 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel0,
changed state to up
And there is no recurive routing message in the log.
Regards,
Hunt
--- "Larson, Chris" <CLarson@usaid.gov> wrote: > You may be getting recursive
routing loops. This is where one end of the
> tunnel is found thru the tunnel interface. Routes to the far end of the
> tunnel should be found outside of the tunnel interface and not thru it. This
> may be why it flaps. If it goes up and down up and down it may be a loop.
>
> You can also check this by getting a snapshot of your routing table before
> the tunnel goes down and then again after. If you notice a route missing in
> the delta between configs then that is prolly the route causing
> recursiveness.
>
>
>
>
> > -----Original Message-----
> > From: Hunt Lee [SMTP:huntl@webcentral.com.au]
> > Sent: Tuesday, March 25, 2003 11:15 PM
> > To: 'Brian Dennis'
> > Cc: 'ccielab@groupstudy.com'
> > Subject: RE: token ring (Frame over a GRE Tunnel)
> >
> > Hi Brian,
> >
> > For doing this FR over a GRE tunnel, do you ever have any problems on the
> > frame-relay pvc just died out...
> >
> > I have used it on a few labs, and on every lab, quite often all of a
> > sudden,
> > the 2 x Frame routers won't be able to ping their opposite Async nor
> > Tunnel
> > interface (even it says up up). But if I do a shut & no shut on the async
> > interface, then it will work again (until it suddens dies again).
> >
> > Have you had any similar experience before?
> >
> > Once again, thanks so much for your help.
> >
> > Regards,
> > Hunt
> >
> >
> >
> > -----Original Message-----
> > From: Brian Dennis [mailto:brian@labforge.com]
> > Sent: Wednesday, 5 March 2003 2:34 AM
> > To: 'Alexander Arsenyev (ETL)'; ccielab@groupstudy.com
> > Subject: RE: token ring (Frame over a GRE Tunnel)
> >
> >
> > Frame-Relay Switching over a GRE Tunnel
> >
> > http://www.labforge.com/configs/frameswitch.htm
> >
> >
> > Brian Dennis, CCIE #2210 (R&S/ISP Dial/Security)
> > brian@labforge.com
> > http://www.labforge.com
http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:45 GMT-3