T2 Serial Interface bouncing

[deepblue61]

I have Cisco 7204, with T3 serial interface and 2 FastEthernet Interfaces.
Recently, my T3 interface is bouncing up and down every night for about 1 hour or 2. Does anyone can help me with some clues why that happened and how to fix it? thanks!
Hereunder are the logs:

Mar 13 20:13:54.318 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
down
Mar 13 20:13:57.318 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
up
Mar 13 20:14:04.638 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 6/0 (cease) 0 by
tes
Mar 13 20:14:04.638 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:14:50.734 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:26:53.850 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:26:53.850 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:31:07.894 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.218) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:32:09.902 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.216) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:32:46.754 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:33:06.790 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:33:06.790 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:33:09.910 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.245) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:34:10.214 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.214) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:35:11.018 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.244) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:38:51.938 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.220) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:39:20.890 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:39:55.342 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.249) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:40:21.294 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:40:35.306 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:40:35.306 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:40:56.646 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.247) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:41:57.550 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.216) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:44:25.406 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:45:24.654 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:45:27.378 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.211) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:45:38.662 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:45:38.662 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:46:31.278 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.215) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 20:46:43.762 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:47:52.522 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
down
Mar 13 20:47:54.558 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
up
Mar 13 20:47:56.522 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
down
Mar 13 20:47:58.558 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
up
Mar 13 20:47:58.558 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:48:46.858 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:49:06.910 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:49:06.910 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:49:50.890 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:50:39.974 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:50:39.974 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:51:51.074 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:53:04.074 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:54:18.074 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:55:03.238 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:55:34.310 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:55:34.310 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:56:49.410 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 20:57:50.722 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:58:33.814 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:58:33.814 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 20:59:16.270 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 20:59:41.330 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 20:59:41.330 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 21:00:45.430 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 21:01:54.430 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 21:02:55.066 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 21:03:09.078 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 21:03:09.078 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 21:04:18.178 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 21:05:11.642 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 21:05:31.686 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 21:05:31.686 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 21:06:42.786 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 21:07:42.826 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 21:08:02.862 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 4/0 (hold time e
xpired) 0 bytes
Mar 13 21:08:02.862 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 21:08:42.494 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 21:08:44.626 est: %BGP-3-NOTIFICATION: received from neighbor 10.144.160.102 6/0 (cease) 0 by
tes
Mar 13 21:08:44.626 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Down BGP Notification received
Mar 13 21:12:19.726 est: %BGP-3-NOTIFICATION: sent to neighbor 10.144.160.102 4/0 (hold time expired
) 0 bytes
Mar 13 21:13:48.626 est: %PIM-6-INVALID_RP_JOIN: Received (*, 224.0.2.213) Join from 10.200.0.2 for
invalid RP 198.140.33.5
Mar 13 21:14:33.254 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
down
Mar 13 21:14:37.290 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2/0, changed state to
up
Mar 13 21:15:24.298 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed st
ate to down
Mar 13 21:15:41.838 est: %BGP-5-ADJCHANGE: neighbor 10.144.160.102 Up
Mar 13 21:15:59.998 est: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed st
ate to up


Thanks!

 

[deepblue61]

Sorry, I meant "T3 Serial Interface bouncing" but not T2 in the title.

 

[BuckWeet]

Well I think obviously the circuit provider needs to be involved.. Its 99% probable that its the facilities..


BuckWeet

 

[deepblue61]

Thanks BuckWeet.

The funny thing is it never bounces during the day. Instead it always bounces druing the night. DO you think there is anything to do with the cofiguration.
I use rip and BGP.

 

[BuckWeet]

No, your problem is a physical layer issue, not a layer 3 and up issue..

Sounds like testing or something is being done on the facilities at night and is causing problems for you as well..

 

[deepblue61]

Thank you so much, Buckweet!
After 2 days of close monitoring, I could see the interface bouncing really happened at night. You probably right, it is physical layer's problem, something must be happened during the night. I'll check with my Telco and let you know the result.