Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
1495
Views
0
Helpful
4
Replies

BGP Error on WAN Router

balakrishnansenthil
Level 1
Level 1

‎09-25-2012 10:02 AM - edited ‎03-07-2019 09:06 AM


Hi Team,

We are getting below errorlogs on WAN01&WAN02 router.

PLease check and let know why this logs happening.

If u need any other logs let me know

Thanks...

Logs From WAN01:
--------------------

*Sep 25 16:29:52.289: BGP: Sched timer-wheel running slow by 1 ticks
*Sep 25 16:29:52.349: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:29:52.350: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:30:52.355: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:30:52.356: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:31:52.361: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:31:52.362: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:32:52.367: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:32:52.368: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:33:52.373: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:33:52.374: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:34:52.379: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:34:52.380: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:35:52.385: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:35:52.386: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:36:52.391: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:36:52.392: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:37:52.397: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:37:52.398: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:38:52.403: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:38:52.404: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:39:52.409: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:39:52.410: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:40:52.415: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:40:52.416: BGP: topo global:IPv4 Multicast:base Scanning routing tables
*Sep 25 16:41:52.421: BGP: topo global:IPv4 Unicast:base Scanning routing tables
*Sep 25 16:41:52.422: BGP: topo global:IPv4 Multicast:base Scanning routing tables
WANCK01#


--------------------------------

Logs From WAN02:
--------------------

*Sep 25 16:38:01.341: TCP0: Connection to 10.154.8.132:14322, advertising MSS 536
*Sep 25 16:38:01.568: TCP0: state was SYNRCVD -> ESTAB [22 -> 10.154.8.132(14322)]
*Sep 25 16:38:01.568: TCB365FE000 setting property TCP_TOS (1) 17033EC9
*Sep 25 16:38:01.569: TCB365FE000 setting property TCP_MSG_NOTIFY (6) 3F605D98
*Sep 25 16:38:08.280: TCB36704E8C created
*Sep 25 16:38:08.280: TCB36704E8C setting property TCP_NO_DELAY (0) 3BB39D34
*Sep 25 16:38:08.280: TCB36704E8C setting property TCP_VRFTABLEID (14) 3BB39D70
*Sep 25 16:38:08.280: TCP: Random local port generated 29707, network 1
*Sep 25 16:38:08.280: TCB36704E8C bound to 10.158.14.92.29707
*Sep 25 16:38:08.280: TCB36704E8C setting property TCP_NONBLOCKING_WRITE (7) 3BB39D90
*Sep 25 16:38:08.280: TCB36704E8C setting property TCP_NONBLOCKING_READ (8) 3BB39D90
*Sep 25 16:38:08.280: TPA: Reserved port 29707 in Transport Port Agent for TCP IP type 1
*Sep 25 16:38:08.280: TCP: sending SYN, seq 1931566347, ack 0
*Sep 25 16:38:08.280: TCP0: Connection to 10.158.15.11:49, advertising MSS 1460
*Sep 25 16:38:08.280: TCP0: state was CLOSED -> SYNSENT [29707 -> 10.158.15.11(49)]
*Sep 25 16:38:08.293: TCP0: state was SYNSENT -> ESTAB [29707 -> 10.158.15.11(49)]
*Sep 25 16:38:08.293: TCP0: tcb 36704E8C connection to 10.158.15.11:49, received MSS 1460, MSS is 1460
*Sep 25 16:38:11.862: TCP0: FIN processed
*Sep 25 16:38:11.862: TCP0: state was ESTAB -> CLOSEWAIT [29707 -> 10.158.15.11(49)]
*Sep 25 16:38:11.863: TCP0: state was CLOSEWAIT -> LASTACK [29707 -> 10.158.15.11(49)]
*Sep 25 16:38:11.863: TCP0: sending FIN
*Sep 25 16:38:11.864: TCP0: Got ACK for our FIN
*Sep 25 16:38:11.864: TCP0: state was LASTACK -> CLOSED [29707 -> 10.158.15.11(49)]
*Sep 25 16:38:11.864: TPA: Released port 29707 in Transport Port Agent for TCP IP type 1 delay 240000
*Sep 25 16:38:11.864: TCB 0x36704E8C destroyed
*Sep 25 16:38:12.536: TCB3F4B938C created
*Sep 25 16:38:12.536: TCB3F4B938C setting property TCP_NO_DELAY (0) 3BB39D24
*Sep 25 16:38:12.536: TCB3F4B938C setting property TCP_VRFTABLEID (14) 3BB39D60
*Sep 25 16:38:12.536: TCP: Random local port generated 19611, network 1
*Sep 25 16:38:12.536: TCB3F4B938C bound to 10.158.14.92.19611
*Sep 25 16:38:12.536: TCB3F4B938C setting property TCP_NONBLOCKING_WRITE (7) 3BB39D80
*Sep 25 16:38:12.536: TCB3F4B938C setting property TCP_NONBLOCKING_READ (8) 3BB39D80
*Sep 25 16:38:12.536: TPA: Reserved port 19611 in Transport Port Agent for TCP IP type 1
*Sep 25 16:38:12.536: TCP: sending SYN, seq 2721593764, ack 0
*Sep 25 16:38:12.536: TCP0: Connection to 10.158.15.11:49, advertising MSS 1460
*Sep 25 16:38:12.536: TCP0: state was CLOSED -> SYNSENT [19611 -> 10.158.15.11(49)]
*Sep 25 16:38:12.537: TCP0: state was SYNSENT -> ESTAB [19611 -> 10.158.15.11(49)]
*Sep 25 16:38:12.537: TCP0: tcb 3F4B938C connection to 10.158.15.11:49, received MSS 1460, MSS is 1460
*Sep 25 16:38:12.544: TCP0: FIN processed
*Sep 25 16:38:12.544: TCP0: state was ESTAB -> CLOSEWAIT [19611 -> 10.158.15.11(49)]
*Sep 25 16:38:12.544: TCP0: state was CLOSEWAIT -> LASTACK [19611 -> 10.158.15.11(49)]
*Sep 25 16:38:12.544: TCP0: sending FIN
*Sep 25 16:38:12.545: TCP0: Got ACK for our FIN
*Sep 25 16:38:12.545: TCP0: state was LASTACK -> CLOSED [19611 -> 10.158.15.11(49)]
*Sep 25 16:38:12.545: TPA: Released port 19611 in Transport Port Agent for TCP IP type 1 delay 240000
*Sep 25 16:38:12.545: TCB 0x3F4B938C destroyed
*Sep 25 16:38:16.519: TCB3F6700D0 created
*Sep 25 16:38:16.519: TCB3F6700D0 setting property TCP_GIVEUP (11) 3F605940
*Sep 25 16:38:16.519: TCP: Random local port generated 23481, network 1
*Sep 25 16:38:16.519: TCB3F6700D0 bound to 10.158.14.92.23481
*Sep 25 16:38:16.519: TPA: Reserved port 23481 in Transport Port Agent for TCP IP type 1
*Sep 25 16:38:16.519: TCP: sending SYN, seq 1730876338, ack 0
*Sep 25 16:38:16.519: TCP0: Connection to 10.158.15.11:49, advertising MSS 1460
*Sep 25 16:38:16.519: TCP0: state was CLOSED -> SYNSENT [23481 -> 10.158.15.11(49)]
*Sep 25 16:38:16.520: TCP0: state was SYNSENT -> ESTAB [23481 -> 10.158.15.11(49)]
WANCK02#
WANCK02#
WANCK02#


Regards,
Senthil

Labels:
0 Helpful
4 Replies 4

cadet alain
VIP Alumni
VIP Alumni

‎09-25-2012 10:20 AM

Hi,

I don't see any error there.

On WAN2 this is debugging of TCP which is logged for communication with TACACS server( port 49).

Regards.

Alain

Don't forget to rate helpful posts.

Don't forget to rate helpful posts.
0 Helpful

balakrishnansenthil
Level 1
Level 1

‎09-25-2012 05:32 PM

Thank you , It mean this error not a problem in this device is it?

Then why it's showing logs I can't see same error on other WAN routers....please make sure clear answer.....

Kindly let me know ASAP.

0 Helpful

cadet alain
VIP Alumni
VIP Alumni
In response to balakrishnansenthil

‎09-25-2012 11:50 PM

Hi,

on WAN2 if you do a show debug you should see debugging for tcp activated, disable it and these logs will disappear.

for first log , scanning of routing table is normal behavior but you should see this log only with debug also so get rid of this debug too and your problem will be solved.

Regards.

Alain

Don't forget to rate helpful posts.

Don't forget to rate helpful posts.
0 Helpful

balakrishnansenthil
Level 1
Level 1
In response to cadet alain

‎09-26-2012 03:03 AM

Hi Alain,

Thanks for your great support,

I will try and let you know update.......

Regards,

Senthil

0 Helpful
Customers Also Viewed These Support Documents