cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
2712
Views
5
Helpful
3
Replies
Highlighted
Beginner

#sh ip bgp summary - Up/Down "never"

Hello.

 

I am receiving alerts from a BGP circuit directly connected to the SP but when i check BGP summary I get this:

 

R1#sh ip bgp sum | inc N|10.1.1.1
Neighbor        V    AS    MsgRcvd  MsgSent TblVer InQ OutQ Up/Down  State/PfxRcd
10.1.1.1         4  65534       0             0           1        0      0       never         Active
R1#!--------------------------------------------------------------------
R1#sh ip route 10.1.1.1
Routing entry for 10.1.1.1/30
Known via "connected", distance 0, metric 0 (connected, via interface)
Routing Descriptor Blocks:
* directly connected, via GigabitEthernet0/1/1.260
Route metric is 0, traffic share count is 1
R1#!--------------------------------------------------------------------
R1#sh int GigabitEthernet0/1/1.260 | inc GigabitEthernet0/1/1.260 |Har|Int|Des|MTU|rel
GigabitEthernet0/1/1.260 is up, line protocol is up
Hardware is SPA-8X1GE-V2, address is ccef.cccc.bbbb (bia ccef.cccc.bbbb)
Description: -xxxxx
Internet address is 10.1.1.1/30
MTU 1500 bytes, BW 150000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255

 

And there is nothing in the logs:

 

R1#sh log | inc Apr 15(.+)BGP(.+)10.1.1.1
R1#sh log | inc Apr 14(.+)BGP(.+)10.1.1.1
R1#

 

The never entry under Up/Down section means that the BGP session has never ever been active? The interface is transmitting and receiving packets, and the alerts are increasing, so I am a bit confused.

 

 

GigabitEthernet0/1/1 is up, line protocol is up
Hardware is SPA-8X1GE-V2, address is ccef.cccc.bbbb (bia ccef.cccc.bbbb)
Description: xxxxx
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive not supported
Full Duplex, 1000Mbps, link type is force-up, media type is SX
output flow-control is on, input flow-control is on
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:01, output hang never
Last clearing of "show interface" counters 2w5d
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 235844
Queueing strategy: Class-based queueing
Output queue: 0/40 (size/max)
5 minute input rate 21000 bits/sec, 27 packets/sec
5 minute output rate 44000 bits/sec, 29 packets/sec
1693423893 packets input, 169097014695 bytes, 0 no buffer
Received 27070 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 3575951 multicast, 0 pause input
1830351220 packets output, 664865214336 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out

 

 

 

 

Thank you

1 ACCEPTED SOLUTION

Accepted Solutions
Contributor

Re: #sh ip bgp summary - Up/Down "never"

If it was up at one point and then lost peering, in that situation "state" should change to idle and under "up/down" should reflect how long it's been down for and not say "never".

3 REPLIES 3
Contributor

Re: #sh ip bgp summary - Up/Down "never"

Router in question is actively trying to establish bgp peering with its neighbor and currently there is no bgp neighbor on that link.

 

Normal output would be like this:

Neighbor        V           AS MsgRcvd MsgSent   TblVer  InQ OutQ   Up/Down  State/PfxRcd
10.10.10.1      4          100       7       6        2    0          0                    00:02:24        1

 

Are you able to ping neighbor's remote address? Can you share bgp configuration?

 

 

 

Beginner

Re: #sh ip bgp summary - Up/Down "never"

I was not able to ping the peer. Unfortunately i cannot trace back to that incident at the moment, as I changed real device name, circuit ID and public IP address when posting details here.

 

I am more concerned about that "never" keyword under Up/Down section. Does it simply mean that the BGP session has never been established? Or is it not so straightforward?

 

 

 

 

Contributor

Re: #sh ip bgp summary - Up/Down "never"

If it was up at one point and then lost peering, in that situation "state" should change to idle and under "up/down" should reflect how long it's been down for and not say "never".

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards