From: Paul Howell (paul.howell@gmail.com)
Date: Tue Aug 07 2007 - 04:40:02 ART
I would take off the backup interface configuration and try to manually get
Serial 2/1 up.  I'm guessing it will do the same thing, come up then go back
down after a short bit.
Is S2/1 connected directly to another router?  Is the other router's
interface enabled?  If so, is the clock rate set on the DCE side?  Also,
check that the layer 2 encapsulation is matching on both sides (both HDLC,
for instance).
- Paul
On 8/4/07, NITIN NITIN <ccie_study_123@yahoo.com> wrote:
>
> Hi Experts ,
>   Please suggest , my backup interface not coming up ......
> Actually , it comes up and after few seconds goes down
>
>   Rack1R5#sh backup
> Primary Interface   Secondary Interface   Status
> -----------------   -------------------   ------
> Serial2/0.54        Serial2/1             backup mode
> Rack1R5#sh backup
> Primary Interface   Secondary Interface   Status
> -----------------   -------------------   ------
> Serial2/0.54        Serial2/1             backup mode
> Rack1R5#
> *Aug  4 15:39:23.275: BACKUP(Serial2/0.54): event = primary interface came
> up
> *Aug  4 15:39:23.275: BACKUP(Serial2/0.54): changed state to "waiting to
> revert"
> *Aug  4 15:39:23.283: BACKUP(Serial2/0.54): event = timer expired on
> primary
> *Aug  4 15:39:23.319: BACKUP(Serial2/0.54): secondary interface
> (Serial2/1) moved to standby
> *Aug  4 15:39:23.319: BACKUP(Serial2/0.54): changed state to "normal
> operation"
> Rack1R5#sh backup
> *Aug  4 15:39:23.387: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
> 173.1.45.4 (Serial2/1) is down: interface down
> Rack1R5#sh backup
> Primary Interface   Secondary Interface   Status
> -----------------   -------------------   ------
> Serial2/0.54        Serial2/1             normal operation
> Rack1R5#
> *Aug  4 15:39:25.291: %LINK-5-CHANGED: Interface Serial2/1, changed state
> to standby mode
> *Aug  4 15:39:26.291: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial2/1, changed state to down
> *Aug  4 15:39:26.291: BACKUP(Serial2/1): event = secondary interface went
> down
> Rack1R5#
> *Aug  4 15:40:04.135: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 10: Neighbor
> 173.1.54.4 (Serial2/0.54) is up: new adjacency
> Rack1R5#sh ip int br
> Rack1R5#sh ip int brief
> Interface                  IP-Address      OK? Method
> Status                Protocol
> FastEthernet0/0            192.10.1.5      YES
> NVRAM  up                    up
> FastEthernet1/0            173.1.5.5       YES
> NVRAM  up                    up
> Serial2/0                  unassigned      YES
> NVRAM  up                    up
> Serial2/0.54               173.1.54.5      YES
> NVRAM  up                    up
> Serial2/0.125              173.1.125.5     YES
> NVRAM  up                    up
> Serial2/1                  173.1.45.5      YES NVRAM  standby
> mode          down
> Serial2/2                  unassigned      YES NVRAM  administratively
> down down
> Serial2/3                  unassigned      YES NVRAM  administratively
> down down
> Loopback0                  150.1.5.5       YES
> NVRAM  up                    up
> Rack1R5#sh run in
> Rack1R5#sh run interface se
> Rack1R5#sh run interface serial 2/0.54
> Building configuration...
>   Current configuration : 156 bytes
> !
> interface Serial2/0.54 point-to-point
> backup interface Serial2/1
> ip address 173.1.54.5 255.255.255.0
> frame-relay interface-dlci 504
>   class R5
> end
>   Rack1R5#sh conf | b map-class
> map-class frame-relay R5
> frame-relay end-to-end keepalive mode bidirectional
>
>
>   Rack1R4#sh conf | b map-class
> map-class frame-relay R4
> frame-relay end-to-end keepalive mode bidirectional
>
>
>   Regards
>
>
> ---------------------------------
> Looking for a deal? Find great prices on flights and hotels with Yahoo!
> FareChase.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:09 ART