Routing

Expand all | Collapse all

extra data bgb summary command

Jump to Best Answer
  • 1.  extra data bgb summary command

    Posted 01-16-2014 19:31
    Hello Everyone!
    Does any one knows what the last four zeros (0/0/0/0) means on the command show bgb summary? For the peer 172.18.2.1 the 10/10/10/0   are the #Active/Received/Accepted/Damped, but can't figure out what the other four zeros mean.  Thanks you in advance!
     
    [edit]
    lab@srxA-2# run show bgp summary 
    Groups: 2 Peers: 4 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                26         10          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    172.18.2.1            65520         50         49       0       0       20:49 10/10/10/0           0/0/0/0
    192.168.1.1           64700         52         53       0       0       21:04 0/10/10/0            0/0/0/0
    192.168.1.2           64700         47         52       0       0       21:03 0/3/3/0              0/0/0/0
    192.168.2.2           64700         46         52       0       0       21:01 0/3/3/0              0/0/0/0

     

     

    [edit]
    lab@srxA-2# run show version 
    Hostname: srxA-2
    Model: srx240h-poe
    JUNOS Software Release [12.1R1.9]

     

     



  • 2.  RE: extra data bgb summary command
    Best Answer

    Posted 01-17-2014 03:38

    Hello,

    Have You tried to read the JUNOS fine manual at all?

    http://www.juniper.net/techpubs/en_US/junos10.4/topics/reference/command-summary/show-bgp-summary.html

     

    Specifically:

     

    If a BGP session is established in the main routing device, the field shows the number of active, received, accepted, and damped routes that are received from a neighbor and appear in the inet.0 (main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the following:
    
        8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer appear in the inet.0 routing table.
        2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer appear in the inet.2 routing table.

     HTH

    Thanks

    Alex



  • 3.  RE: extra data bgb summary command

    Posted 01-17-2014 12:10
    I read the documentation, but perhaps you misundertood my question. My question refers to the extra four number on the output; those in red, not the one in blue (see output below). As you can the see, my output have an additional four digits; all zeros. They do not refer to the active, received, etc routes. Those are the first set of numbers (e.g. 10/10/10/0). The other set of number do not appear on the Junos documentation for the "show bgb summary" command.  
     
    [edit]
    lab@srxA-2# run show bgp summary 
    Groups: 2 Peers: 4 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                26         10          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    172.18.2.1            65520         50         49       0       0       20:49 10/10/10/0           0/0/0/0
    192.168.1.1           64700         52         53       0       0       21:04 0/10/10/0            0/0/0/0
    192.168.1.2           64700         47         52       0       0       21:03 0/3/3/0              0/0/0/0
    192.168.2.2           64700         46         52       0       0       21:01 0/3/3/0              0/0/0/0

     

     

    [edit]
    lab@srxA-2# run show version 
    Hostname: srxA-2
    Model: srx240h-poe
    JUNOS Software Release [12.1R1.9]
     
    Junos documentation does not have the extra set of number highlighted in red in my output
    user@host> show bgp summary
    Groups: 2 Peers: 4 Down peers: 1
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                 6          4          0          0          0          0
    Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn 
    State|#Active/Received/Damped...
    10.0.0.3        65002         86         90       0       2       42:54 0/0/0                
    0/0/0
    10.0.0.4        65002         90         91       0       1       42:54 0/2/0                
    0/0/0
    10.0.0.6        65002         87         90       0       3           3 Active
    10.1.12.1       65001         89         89       0       1       42:54 4/4/0                
    0/0/0


  • 4.  RE: extra data bgb summary command

    Posted 01-17-2014 13:42

    I think what niev and the article was saying, in your case, that 0/0/0/0 means you do not have another instance with bgp established. So the rest of the section from the article explains more:

     

    • If a BGP session is established on the main routing device, the field shows the number of active, received, accepted, and damped routes that are received from a neighbor and appear in the inet.0 (main) and inet.2 (multicast) routing tables. For example, 8/10/10/2 and 2/4/4/0 indicate the following:
      • 8 active routes, 10 received routes, 10 accepted routes, and 2 damped routes from a BGP peer appear in the inet.0 routing table.
      • 2 active routes, 4 received routes, 4 accepted routes, and no damped routes from a BGP peer appear in the inet.2 routing table.
    • If a BGP session is established in a routing instance, the field indicates the established (Establ) state, identifies the specific routing table that receives BGP updates, and shows the number of active, received, and damped routes that are received from a neighbor. For example, Establ VPN-AB.inet.0: 2/4/0 indicates the following:
      • The BGP session is established.
      • Routes are received in the VPN-AB.inet.0 routing table.
      • The local routing device has two active routes, four received routes, and no damped routes from a BGP peer.

      So in your case, 0/0/0/0 is the equivalent of 2/4/0/0. You dont have another established session, so the 0/0/0/0 is just a place holder value.

      I have to agree with you though, Juniper may not really pride itself as coming up the best explanations. I can site numerous examples where I am left confused and go to somebody else website and get a total understanding.



  • 5.  RE: extra data bgb summary command

    Posted 01-17-2014 18:10

    The article provided aarseniev does show the information I am referring by do not explain anything about it.

    show bgp summary (When a Peer Is Established)

     
    user@host> show bgp summary
    Groups: 1 Peers: 3 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                 6          4          0          0          0          0
    Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn 
    State|#Active/Received/Damped...
    10.0.0.2        65002      88675      88652       0       2       42:38        2/4/0   2 active, 4 received, 0 damped             
    0/0/0 no explanation on the article
    10.0.0.3        65002      54528      54532       0       1     2w4d22h 0/0/0               
     0/0/0
    10.0.0.4        65002      51597      51584       0       0     2w3d22h 2/2/0                
    0/0/0
     

    I have only see those additional number on the SRXs. The MX-80 display the information as I should expect. Below is the output of the same command on an MX-80. It does not have the additional set of zeros 0/0/0/0 .

    lab@mxA-1# run show bgp summary     
    Groups: 3 Peers: 3 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0               
                           2          2          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.0.10.1             65512        257        257       0       0     1:55:06 Establ Routing Instance
      ceA-1.inet.0: 1/1/1/0
    10.0.10.2             65101        256        257       0       0     1:55:06 Establ  Master Instance
     inet.0: 1/1/1/0
     
    193.168.1.2           65512        258        256       0       0     1:55:00 Establ
      inet.0: 1/1/1/0
     

    Those extra zeros does not show up in any of the other commands (e.g. show bgp neighbor), so I am going to assume that they are superfluous. 

     

     
    [edit]
    lab@srxA-1# run show bgp summary    
    Groups: 2 Peers: 4 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                26         10          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    172.18.1.1            65510         11         10       0       0        2:25 10/10/10/0           0/0/0/0
    192.168.1.2           64700          8         12       0       0        2:37 0/3/3/0              0/0/0/0
    192.168.2.1           64700          6          6       0       0          20 0/10/10/0            0/0/0/0
    192.168.2.2           64700          2          6       0       0          15 0/3/3/0              0/0/0/0
     
    [edit]
    lab@srxA-1# run show bgp group 
    Group Type: Internal    AS: 64700                  Local AS: 64700
      Name: my-int-group    Index: 0                   Flags: <Export Eval>
      Export: [ change-next-hop ] 
      Options: <AdvertiseInactive>
      Holdtime: 0
      Total peers: 3        Established: 3
      192.168.1.2+179
      192.168.2.1+58533
      192.168.2.2+179
      inet.0: 0/16/16/0
     
    Group Type: External                               Local AS: 64700
      Name: my-ext-group    Index: 1                   Flags: <Export Eval>
      Export: [ adv-aggregates ] 
      Options: <AdvertiseInactive>
      Holdtime: 0
      Total peers: 1        Established: 1
      172.18.1.1+179
      inet.0: 10/10/10/0
     
    Groups: 2  Peers: 4    External: 1    Internal: 3    Down peers: 0   Flaps: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                26         10          0          0          0          0
                                            
    [edit]
    lab@srxA-1# run show bgp neighbor 
    Peer: 172.18.1.1+179 AS 65510  Local: 172.18.1.2+58555 AS 64700
      Type: External    State: Established    Flags: <ImportEval Sync>
      Last State: OpenConfirm   Last Event: RecvKeepAlive
      Last Error: None
      Export: [ adv-aggregates ] 
      Options: <Preference AdvertiseInactive PeerAS Refresh>
      Holdtime: 90 Preference: 170
      Number of flaps: 0
      Peer ID: 10.10.10.10     Local ID: 192.168.1.1       Active Holdtime: 90
      Keepalive Interval: 30         Peer index: 0   
      BFD: disabled, down
      Local Interface: ge-0/0/3.0                       
      NLRI for restart configured on peer: inet-unicast
      NLRI advertised by peer: inet-unicast
      NLRI for this session: inet-unicast
      Peer supports Refresh capability (2)
      Stale routes from peer are kept for: 300
      Peer does not support Restarter functionality
      NLRI that restart is negotiated for: inet-unicast
      NLRI of received end-of-rib markers: inet-unicast
      NLRI of all end-of-rib markers sent: inet-unicast
      Peer supports 4 byte AS extension (peer-as 65510)
      Peer does not support Addpath
      Table inet.0 Bit: 10001               
        RIB State: BGP restart is complete
        Send state: in sync
        Active prefixes:              10
        Received prefixes:            10
        Accepted prefixes:            10
        Suppressed due to damping:    0
        Advertised prefixes:          5
      Last traffic (seconds): Received 12   Sent 12   Checked 57  
      Input messages:  Total 20     Updates 5       Refreshes 0     Octets 549
      Output messages: Total 19     Updates 2       Refreshes 0     Octets 516
      Output Queue[0]: 0
     
    Peer: 192.168.1.2+179 AS 64700 Local: 192.168.1.1+51298 AS 64700
      Type: Internal    State: Established    Flags: <ImportEval Sync>
      Last State: OpenConfirm   Last Event: RecvKeepAlive
      Last Error: None
      Export: [ change-next-hop ] 
      Options: <Preference LocalAddress AdvertiseInactive Refresh>
      Local Address: 192.168.1.1 Holdtime: 90 Preference: 170
      Number of flaps: 0
      Peer ID: 192.168.1.2     Local ID: 192.168.1.1       Active Holdtime: 90
      Keepalive Interval: 30         Peer index: 0   
      BFD: disabled, down                   
      NLRI for restart configured on peer: inet-unicast
      NLRI advertised by peer: inet-unicast
      NLRI for this session: inet-unicast
      Peer supports Refresh capability (2)
      Stale routes from peer are kept for: 300
      Peer does not support Restarter functionality
      NLRI that restart is negotiated for: inet-unicast
      NLRI of received end-of-rib markers: inet-unicast
      NLRI of all end-of-rib markers sent: inet-unicast
      Peer supports 4 byte AS extension (peer-as 64700)
      Peer does not support Addpath
      Table inet.0 Bit: 10000
        RIB State: BGP restart is complete
        Send state: in sync
        Active prefixes:              0
        Received prefixes:            3
        Accepted prefixes:            3
        Suppressed due to damping:    0
        Advertised prefixes:          10
      Last traffic (seconds): Received 25   Sent 25   Checked 73  
      Input messages:  Total 17     Updates 2       Refreshes 0     Octets 364
      Output messages: Total 21     Updates 4       Refreshes 0     Octets 655
      Output Queue[0]: 0                    
     
    Peer: 192.168.2.1+58533 AS 64700 Local: 192.168.1.1+179 AS 64700
      Type: Internal    State: Established    Flags: <ImportEval Sync>
      Last State: OpenConfirm   Last Event: RecvKeepAlive
      Last Error: None
      Export: [ change-next-hop ] 
      Options: <Preference LocalAddress AdvertiseInactive Refresh>
      Local Address: 192.168.1.1 Holdtime: 90 Preference: 170
      Number of flaps: 0
      Peer ID: 192.168.2.1     Local ID: 192.168.1.1       Active Holdtime: 90
      Keepalive Interval: 30         Peer index: 1   
      BFD: disabled, down
      NLRI for restart configured on peer: inet-unicast
      NLRI advertised by peer: inet-unicast
      NLRI for this session: inet-unicast
      Peer supports Refresh capability (2)
      Stale routes from peer are kept for: 300
      Peer does not support Restarter functionality
      NLRI that restart is negotiated for: inet-unicast
      NLRI of received end-of-rib markers: inet-unicast
      NLRI of all end-of-rib markers sent: inet-unicast
      Peer supports 4 byte AS extension (peer-as 64700)
      Peer does not support Addpath         
      Table inet.0 Bit: 10000
        RIB State: BGP restart is complete
        Send state: in sync
        Active prefixes:              0
        Received prefixes:            10
        Accepted prefixes:            10
        Suppressed due to damping:    0
        Advertised prefixes:          10
      Last traffic (seconds): Received 2    Sent 25   Checked 19  
      Input messages:  Total 16     Updates 5       Refreshes 0     Octets 541
      Output messages: Total 15     Updates 4       Refreshes 0     Octets 541
      Output Queue[0]: 0
     
    Peer: 192.168.2.2+179 AS 64700 Local: 192.168.1.1+61846 AS 64700
      Type: Internal    State: Established    Flags: <ImportEval Sync>
      Last State: OpenConfirm   Last Event: RecvKeepAlive
      Last Error: None
      Export: [ change-next-hop ] 
      Options: <Preference LocalAddress AdvertiseInactive Refresh>
      Local Address: 192.168.1.1 Holdtime: 90 Preference: 170
      Number of flaps: 0
      Peer ID: 192.168.2.2     Local ID: 192.168.1.1       Active Holdtime: 90
      Keepalive Interval: 30         Peer index: 2   
      BFD: disabled, down
      NLRI for restart configured on peer: inet-unicast
      NLRI advertised by peer: inet-unicast
      NLRI for this session: inet-unicast
      Peer supports Refresh capability (2)
      Stale routes from peer are kept for: 300
      Peer does not support Restarter functionality
      NLRI that restart is negotiated for: inet-unicast
      NLRI of received end-of-rib markers: inet-unicast
      NLRI of all end-of-rib markers sent: inet-unicast
      Peer supports 4 byte AS extension (peer-as 64700)
      Peer does not support Addpath
      Table inet.0 Bit: 10000
        RIB State: BGP restart is complete
        Send state: in sync
        Active prefixes:              0
        Received prefixes:            3
        Accepted prefixes:            3
        Suppressed due to damping:    0
        Advertised prefixes:          10
      Last traffic (seconds): Received 17   Sent 25   Checked 10  
      Input messages:  Total 11     Updates 2       Refreshes 0     Octets 250
      Output messages: Total 15     Updates 4       Refreshes 0     Octets 541
      Output Queue[0]: 0


  • 6.  RE: extra data bgb summary command

    Posted 01-17-2014 23:25

    The article provided aarseniev does show the information I am referring by do not explain anything about it.

    show bgp summary (When a Peer Is Established)

     
    user@host> show bgp summary
    Groups: 1 Peers: 3 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                 6          4          0          0          0          0
    Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn 
    State|#Active/Received/Damped...
    10.0.0.2        65002      88675      88652       0       2       42:38        2/4/0   2 active, 4 received, 0 damped             
    0/0/0 no explanation on the article//// Article explanation: IF a BGP session is established in a routing instance, the field indicates the established (Establ) state, identifies the specific routing table that receives BGP updates, and shows the number of active, received, and damped routes that are received from a neighbor. For example, Establ VPN-AB.inet.0: 2/4/0 indicates the following:
    • The BGP session is established.////
    10.0.0.3        65002      54528      54532       0       1     2w4d22h 0/0/0               
     0/0/0
    10.0.0.4        65002      51597      51584       0       0     2w3d22h 2/2/0                
    0/0/0
    Do you have a routing instance on this device with an bgp session established. From the output, I would say no, you do not have a routing instance with bgp configured that has been established. However if you do, please provide the following output:
    user@host> show configuration routing-instance
     
    =================================================

    lab@srxA-2# run show bgp summary
    Groups: 3 Peers: 6 Down peers: 0
    Table Tot Paths Act Paths Suppressed History Damp State Pending
    inet.0 36 10 0 0 0 0
    Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    172.18.2.1 65520 50 48 0 0 20:47 Establ
    inet.0: 10/10/10/0
    172.18.12.1 65520 49 47 0 0 20:46 Establ
    inet.0: 0/10/10/0
    172.20.77.1 64700 18 19 0 0 7:32 Establ
    TestR2.inet.0: 0/0/0/0
    192.168.1.1 64700 51 52 0 0 20:45 Establ
    inet.0: 0/10/10/0
    192.168.1.2 64700 46 50 0 0 20:42 Establ
    inet.0: 0/3/3/0
    192.168.2.2 64700 48 50 0 0 20:44 Establ
    inet.0: 0/3/3/0


    I am not sharing any routes with the RI neighbors.
    =============================================================

    I have only see those additional number on the SRXs. The MX-80 display the information as I should expect. Below is the output of the same command on an MX-80. It does not have the additional set of zeros 0/0/0/0 . And it should not because we see the routing instance with established neighbors! So we are good here!

    lab@mxA-1# run show bgp summary     
    Groups: 3 Peers: 3 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0               
                           2          2          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    10.0.10.1             65512        257        257       0       0     1:55:06 Establ Routing Instance
      ceA-1.inet.0: 1/1/1/0
    10.0.10.2             65101        256        257       0       0     1:55:06 Establ  Master Instance
     inet.0: 1/1/1/0
     
    193.168.1.2           65512        258        256       0       0     1:55:00 Establ
      inet.0: 1/1/1/0
     ===================================================================

    Those extra zeros does not show up in any of the other commands (e.g. show bgp neighbor), so I am going to assume that they are superfluous. 

    >show bgp neighbor is specific now and not a summary. Since there are no neighbors in a routing instance on the srx and the router, where would you expect to see the missing zeros show up from a command that is looking for neighbors? 

    Different commands will provide different information. However if you had a routing instance and you ran the command it would still show you information in a different format, for example:

    Table TestRI.inet.0 Bit: 20000
    RIB State: BGP restart is complete
    RIB State: VPN restart is complete
    Send state: in sync
    Active prefixes: 0
    Received prefixes: 0
    Accepted prefixes: 0
    Suppressed due to damping: 0

     I am not sending any routes.

    BTW,  Could you provide this information:

    lab@mxA-1# run show bgp neighbor

     ====================================================================
    [edit]
    lab@srxA-1# run show bgp summary    
    Groups: 2 Peers: 4 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                26         10          0          0          0          0
    Peer                     AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
    172.18.1.1            65510         11         10       0       0        2:25 10/10/10/0           0/0/0/0(place holders)
    192.168.1.2           64700          8         12       0       0        2:37 0/3/3/0              0/0/0/0
    192.168.2.1           64700          6          6       0       0          20 0/10/10/0            0/0/0/0
    192.168.2.2           64700          2          6       0       0          15 0/3/3/0              0/0/0/0
     
    Do you have routing instance with bgp established in the routing instance on this device? if the answere is no, then the output is correct. If the answer is yes please provide the following output:
    lab@srxA-1#show routing-instances
     Seems like we are missing the question, but let me summarize and you can correct misunderstanding.
    Original question was what do those extra zeroes mean? 
    Ans: The zeroes are place holders for a bgp session established in a routing instance.
    Different conclusion: They do not show up in any other commands fro example show bgp neighbor, therefore they are superfluous.
    Comment: the absence of an output from a different command is by design, however in the even of established peer with neighbors in a routing instance, the values show up but in a different format because that is no longer a summary format. 

     



  • 7.  RE: extra data bgb summary command

    Posted 01-18-2014 00:02

    Hi there,

    The Juniper documentation link I posted DOES have this set of numbers three, not four but this also applies), it is just so wierdly formatted so not anyone can spot them.

     

    show bgp summary (When a Peer Is Established)
    user@host> show bgp summary
    
    Groups: 1 Peers: 3 Down peers: 0
    Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
    inet.0                 6          4          0          0          0          0
    Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn 
    State|#Active/Received/Damped...
    10.0.0.2        65002      88675      88652       0       2       42:38 2/4/0                
    0/0/0
    10.0.0.3        65002      54528      54532       0       1     2w4d22h 0/0/0               
     0/0/0
    10.0.0.4        65002      51597      51584       0       0     2w3d22h 2/2/0                
    0/0/0
    

     

    I hope the documentation now makes sense to You.

    If not I spell it out - the nimbers in Your latest post in red refer to number of BGP routes in INET.2 table.

    As long as You don't have BGP "family inet-multicast" routes coming from Your peers, these will be always zero.

    HTH

    Thanks
    Alex

     



  • 8.  RE: extra data bgb summary command

    Posted 01-18-2014 09:46

    Thank you everyone!! I just got what everything was trying to explain. It suddenly click. I appreciate everyones input and willingness to help. Sorry for dragging the conversation this long when everything was explained on the first post.