Examples
 
                           		
                           The following
                              		  example shows sample output from the 
                              		  show bgp bmp 
                              		  command when the 
                              		  summary 
                              		  keyword is used: 
                              		
                           
 
                           		
RP/0/RSP0/CPU0:router# show bgp bmp summary
ID   Host                Port     State   Time        NBRs
 1   10.0.101.1          16666    ESTAB   00:29:52    1   
 2   10.0.101.2          16667    ESTAB   00:29:52    0   
 3   fed0::1001          26666    ESTAB   00:29:52    0   
 4   fed0::1002          26667    ESTAB   00:29:52    0   
 5   10.0.101.1          16666    ESTAB   00:21:49    0   
 6   10.0.101.1          16666    ESTAB   00:29:52    0   
 7   fed0::1001          26666    ESTAB   00:29:52    0   
 8   fed0::1001          26666    ESTAB   00:29:52    0 
 
                           		The following
                              		  example shows sample output from the 
                              		  show bgp bmp 
                              		  command when the 
                              		  server 
                              		  keyword, with server ID as 4, is used: 
                              		
                           
 
                           		
RP/0/RSP0/CPU0:router# show bgp bmp server 4
BMP server 4
Host 10.0.101.1 Port 16666
Connected for 00:25:07
Precedence:  internet
BGP neighbors: 1
VRF: - (0x60000000)
Update Source: 9.9.9.9 (Lo9)
Update Source Vrf ID: 0x60000000
Message Stats:
Total messages sent: 60
         INITIATION: 1
        TERMINATION: 0
       STATS-REPORT: 0
  PER-PEER messages: 59
  Neighbor 20.0.101.11
Messages pending: 0
Messages sent: 59
      PEER-UP: 1
    PEER-DOWN: 0
    ROUTE-MON: 58
                           			
                           			
                           			The show bgp bmp summary  command displays BMP server summary information such as server address and port number, server state, time for which server
                              is up and the number of neighbors the server is monitoring. 
                           
                           			
                           
                              				
Router#show bgp bmp summary 
ID   Host                 Port     State   Time        NBRs 
 1   12.1.2.1             16001    ESTAB   01:35:05    14   
 2   12.2.2.1             16002    ESTAB   01:30:47    11 
                              			
                           			
                           The show bgp bmp server <ID>  command displays BMP server details, BMP update modes exported to the BMP server, configured (or default) values specific
                              to the update modes, update generation details, TCP connection status, BMP server specific message statistics, and statistics
                              of the neighbors monitored by the BMP server. 
Router#show bgp bmp server 1      
BMP server 1 
Host 12.1.2.1 Port 16001 
Connected for 01:19:20 
Last Disconnect event received : 00:00:00 
Precedence:  internet 
BGP neighbors: 14 
VRF: - (0x60000000) 
Update Source: - (-) 
Update Source Vrf ID: 0x0 
Update Mode                       : In-Post-Policy, Local-RIB 
  In-Post-Policy 
   Advertisement interval         : 15 secs 
   Scanner interval               : 60 secs 
  Local-RIB 
   Advertisement interval         : 15 secs 
   Scanner interval 
     Global                       : 60 secs 
     IPv4 Unicast                 : 60 secs 
     VPNv4 Unicast                : 60 secs 
     IPv6 Unicast                 : 60 secs 
     VPNv6 Unicast                : 60 secs 
Flapping Delay                    : 300 secs 
Initial Delay                     : 0 secs 
Initial Refresh Delay             : 1 secs 
Initial Refresh Spread            : 1 secs 
Stats Reporting Period            : 0 secs 
Queue Route Mon Msg buffer limit  : 133693 KB (Current Server Up Count: 2) 
Queue Route Mon Msg buffer usage  : 0 B 
Queue write pulse sent            : Feb  6 12:32:13.676, not set (all) 
Queue write pulse received        : Feb  6 12:32:13.676 
Update Generation in Progress     : No 
Reset Walk in Progress            : No 
IPv4 Unicast         
  Version                     : 11 
  Init EOR Version            : 11 
  Init EOR Pending count      : 0 
  Update Generation  
    Last Run                   : Feb  6 12:32:04.615, Count 1 
    Walk Currently Stalled     : No, Last Stalled : not set, Count 0 
VPNv4 Unicast        
  Version                     : 14 
  Init EOR Version            : 14 
  Init EOR Pending count      : 0 
  Update Generation  
    Last Run                   : Feb  6 12:32:04.615, Count 1 
    Walk Currently Stalled     : No, Last Stalled : not set, Count 0 
IPv6 Unicast         
  Version                     : 12 
  Init EOR Version            : 12 
  Init EOR Pending count      : 0 
  Update Generation  
    Last Run                   : Feb  6 12:32:04.615, Count 1 
    Walk Currently Stalled     : No, Last Stalled : not set, Count 0 
VPNv6 Unicast        
  Version                     : 16 
  Init EOR Version            : 16 
  Init EOR Pending count      : 0 
  Update Generation  
    Last Run                   : Feb  6 12:32:04.615, Count 1 
    Walk Currently Stalled     : No, Last Stalled : not set, Count 0 
  
TCP:  
  Last message sent: Feb  6 12:32:04.615, Status: No Pending Data 
  Last write pulse received: Feb  6 12:32:04.863, Waiting: FALSE 
Message Stats: 
Total msgs dropped   : 0 
Total msgs pending   : 0, Max: 19 at Feb  6 12:32:04.615 
Total messages sent  : 100 
Total bytes sent     : 13148, Time spent: 0.000 secs 
  INITIATION         : 1 
  TERMINATION        : 0 
  STATS-REPORT       : 0 
  PER-PEER messages  : 99  
  ROUTE-MON messages : 88 
   EOR messages      : 30 
   Update messages   : 58 (Prefixes: 41, Err: 0)  
Update gen time spent: 0.000 secs 
Neighbor 12.100.0.1 (vrf foo) 
  Messages pending : 0 
  Messages dropped : 0 
  Messages sent    : 5 
    PEER-UP        : 1 
    PEER-DOWN      : 0 
    ROUTE-MON      : 4 
      EOR          : 2 
      Update       : 2 (Prefixes: 4, Err: 0)  
Neighbor 12:100::1 (vrf foo) 
  Messages pending : 0 
  Messages dropped : 0 
  Messages sent    : 3 
    PEER-UP        : 1 
    PEER-DOWN      : 0 
    ROUTE-MON      : 2 
      EOR          : 1 
      Update       : 1 (Prefixes: 2, Err: 0)  
Neighbor 12.101.0.1 (vrf bar) 
  Messages pending : 0 
  Messages dropped : 0 
  Messages sent    : 5 
    PEER-UP        : 1 
    PEER-DOWN      : 0 
    ROUTE-MON      : 4 
      EOR          : 2 
      Update       : 2 (Prefixes: 4, Err: 0)  
Neighbor 12.0.0.1 (vrf default) 
  Messages pending : 0 
  Messages dropped : 0 
  Messages sent    : 7 
    PEER-UP        : 1 
    PEER-DOWN      : 0 
    ROUTE-MON      : 6 
      EOR          : 4 
      Update       : 2 (Prefixes: 4, Err: 0) 
                           			
                           The show bgp bmp server <ID>   command with the wide  command displays the same information as show bgp bmp server <ID>  except that it displays the neighbor information in a wide tabular format. 
Router#show bgp bmp server 1 wide 
BMP server 1 
Host 12.1.2.1 Port 16001 
Connected for 01:00:49 
Last Disconnect event received : 00:00:00 
Precedence:  internet 
BGP neighbors: 14 
VRF: - (0x60000000) 
Update Source: - (-) 
Update Source Vrf ID: 0x0 
.. 
<truncated> .. 
Message Stats: 
Total msgs dropped   : 0 
Total msgs pending   : 0, Max: 19 at Feb  6 12:32:04.615 
Total messages sent  : 100 
Total bytes sent     : 13148, Time spent: 0.000 secs 
  INITIATION         : 1 
  TERMINATION        : 0 
  STATS-REPORT       : 0 
  PER-PEER messages  : 99 
  ROUTE-MON messages : 88 
   EOR messages      : 30 
   Update messages   : 58 (Prefixes: 41, Err: 0)  
Update gen time spent: 0.000 secs 
 Legend: 
  MsgPend   : Messages yet to be sent 
  MsgDrop   : Messages dropped 
  MsgSent   : Messages sent 
  PeerUp    : Peer-Up messages sent 
  PeerDown  : Peer-Down messages sent 
  RouteMon  : Router-Monitoring messages sent 
  EOR       : EOR messages sent 
  Update    : Update messages sent 
  UpdPaths  : Paths advertised in Update messages 
  UpdErrs   : Paths not advertised in Update messages 
  Withdraw  : Withdraw messages sent 
  WdrwPaths : Paths advertised in Withdraw messages 
  WdrwErrs  : Paths not advertised in Withdraw messages 
Neighbor                 VRF                     MsgPend    MsgDrop    MsgSent     PeerUp   PeerDown   RouteMon        EOR     Update   UpdPaths    UpdErrs   Withdraw  WdrwPaths   WdrwErrs 
12.100.0.1               foo                           0          0          5          1          0          4          2          2          4          0          0          0          0 
12:100::1                foo                           0          0          3          1          0          2          1          1          2          0          0          0          0 
12.101.0.1               bar                           0          0          5          1          0          4          2          2          4          0          0          0          0 
12.0.0.1                 default                       0          0          7          1          0          6          4          2          4          0          0          0          0 
                           			
                           The show bgp bmp server <ID>  command displays the advertisement-interval time that you configured.
Router#show bgp bmp server 1 
BMP server 1 
Host 12.1.2.1 Port 16001 
Connected for 04:22:39 
Last Disconnect event received : 00:00:00 
Precedence:  internet 
BGP neighbors: 10 
VRF: - (0x60000000) 
Update Source: - (-) 
Update Source Vrf ID: 0x0 
Update Mode                       : In-Post-Policy, Local-RIB 
  In-Post-Policy 
   Advertisement interval         : 15 secs 
   Scanner interval               : 60 secs 
  Local-RIB 
   Advertisement interval         : 15 secs 
   Scanner interval 
     Global                       : 60 secs 
     IPv4 Unicast                 : 60 secs 
     VPNv4 Unicast                : 60 secs 
     IPv6 Unicast                 : 60 secs 
     VPNv6 Unicast                : 60 secs 
Flapping Delay                    : 300 secs 
Initial Delay                     : 0 secs 
Initial Refresh Delay             : 1 secs 
Initial Refresh Spread            : 1 secs 
Stats Reporting Period            : 0 secs 
Queue Route Mon Msg buffer limit  : 133693 KB (Current Server Up Count: 2) 
Queue Route Mon Msg buffer usage  : 0 B 
Queue write pulse sent            : Dec 16 15:19:36.755, not set (all) 
-----More------ 
                           			
                           The show bgp bmp server <ID>  command displays the BMP scan time that you configured. 
Router#show bgp bmp server 1  
BMP server 1 
Host 12.1.2.1 Port 16001 
Connected for 04:22:39 
Last Disconnect event received : 00:00:00 
Precedence:  internet 
BGP neighbors: 10 
VRF: - (0x60000000) 
Update Source: - (-) 
Update Source Vrf ID: 0x0 
Update Mode                       : In-Post-Policy, Local-RIB 
  In-Post-Policy 
   Advertisement interval         : 15 secs 
   Scanner interval               : 60 secs 
  Local-RIB 
   Advertisement interval         : 15 secs 
   Scanner interval 
     Global                       : 60 secs 
     IPv4 Unicast                 : 60 secs 
     VPNv4 Unicast                : 60 secs 
     IPv6 Unicast                 : 60 secs 
     VPNv6 Unicast                : 60 secs 
Flapping Delay                    : 300 secs 
Initial Delay                     : 0 secs 
Initial Refresh Delay             : 1 secs 
Initial Refresh Spread            : 1 secs 
Stats Reporting Period            : 0 secs 
Queue Route Mon Msg buffer limit  : 133693 KB (Current Server Up Count: 2) 
Queue Route Mon Msg buffer usage  : 0 B 
Queue write pulse sent            : Dec 16 15:19:36.755, not set (all) 
-----More------ 
 
                           			
                           The show bgp bmp table  command displays summary information of prefixes and paths learnt from the monitored BGP neighbors. 
Router#show bgp bmp table 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
BMP prefix table version : 11 
Number of prefixes: 5, paths: 9 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
   100.1.1.3/32       7          23.0.1.3         0x03/0xfc  0x02   1 
   100.1.2.3/32       11         23:0:2::3        0x03/0xfc  0x02   1 
    100.1.2.3/32      11         23.0.2.3         0x03/0xfc  0x02   1 
   100.1.3.3/32       10         23.0.2.3         0x03/0xfc  0x03   1 
    100.1.3.3/32      10         23.0.1.3         0x03/0xfc  0x03   1 
   200.1.1.1/32       5          12::1            0x03/0xfc  0x00    
    200.1.1.1/32      5          12.0.0.1         0x03/0xfc  0x00    
   200.2.1.1/32       6          12::1            0x03/0xfc  0x00    
    200.2.1.1/32      6          12.0.0.1         0x03/0xfc  0x00 
                           			
                           If a prefix has more than one path, the prefix is printed multiple times, once for each path, except that for the second paths
                              onwards, the prefix is indented by one space as visible in case of the prefix 100.1.2.3 in the above table. This prefix has
                              a path via neighbor 23:0:2::3 and 23.0.2.3. 
                           
                           			
                           The Bit Map displayed above has 2 bitmap values. The first value is the bitmap of BMP servers to which the prefix is advertised and the
                              second value is the bitmap of BMP servers to which the prefix is yet to be advertized. Bit n in both the bitmaps (where n is 0 to 7) represent Server m where m = n + 1. For example, bit 3 represents Server 4. 
                           
                           			
                           If the advertized bitmap is 0x03 (00000011b) it means that the prefix is advertized to servers 1 and 2. Simularly, if the yet to be advertized bitmap is 0xfc, then it means that the prefix is yet to be advertized to servers 3, 4, 5, 6, 7 and 8. However if any of these
                              servers is not configured, then the corresponding bits can be ignored. 
                           
                           			
                           You can run the show bgp bmp table  command as follows:
                           
                           			
                           
                              				
                              - 
                                 					
                                 For a specific address family identifiers (AFI) or sub-address family identifiers (SAFI). For example, show bgp bmp vpnv4 unicast  table, or a specific BMP monitoring mode, for example show bgp bmp mode inbound post-policy  table.
                                  
- 
                                 					
                                 If you do not specify the AFI and SAFI, the command displays information for the default AFI IPv4 Unicast.
                                  
- 
                                 					
                                 If you do not specify the BMP monitoring mode, the command displays information for the default mode Inbound Post-Policy.
                                  For example, if you run the command show bgp bmp table  where the BMP monitoring mode or the AFI are not specified, the command displays information for Inbound Post-Policy BMP mode IPv4 Unicast AFI. 
                                  
- 
                                 					
                                 For all BMP monitoring modes (mode all) and/or all AFIs (all all).  
The following example shows a brief summary of the prefixes for BMP mode Local-RIB and IPv4 Unicast AFI:
Router#show bgp bmp mode local-rib table 
---------------------------------------------- 
Route monitoring mode : Local-RIB 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
BGP main routing table version : 9 
Number of prefixes: 4, paths: 4 
   Network            Next Hop            Metric LocPrf Path 
   100.1.1.3/32       23.0.1.3                 0    100 ? 
   100.1.2.3/32       23.0.2.3                 0    100 ? 
   200.1.1.1/32       12.0.0.1                 0        1 ? 
   200.2.1.1/32       12.0.0.1                 0        1 ? 
Processed 4 prefixes, 4 paths 
 
                           			
                           			
                           The following example shows a brief summary of the prefixes for BMP mode Inbound Post-Policy and VPNv4 Unicast AFI:
Router#show bgp bmp vpnv4 unicast table 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
BMP prefix table version : 14 
Number of RDs: 3, prefixes: 6, paths: 10 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
Route Distinguisher: 2:100 (default for vrf foo), Version 6 
   200.1.1.1/32       5          12.100.0.1       0x03/0xfc  0x00    
   200.2.1.1/32       6          12.100.0.1       0x03/0xfc  0x00    
Route Distinguisher: 2:101 (default for vrf bar), Version 8 
   200.1.1.1/32       7          12.101.0.1       0x03/0xfc  0x00    
   200.2.1.1/32       8          12.101.0.1       0x03/0xfc  0x00    
Route Distinguisher: 2:200, Version 14 
   200.1.1.4/32       14         23.0.1.3         0x03/0xfc  0x02    
    200.1.1.4/32      14         23.0.2.3         0x03/0xfc  0x02    
    200.1.1.4/32      14         23:0:2::3        0x03/0xfc  0x02    
   200.2.1.4/32       13         23.0.1.3         0x03/0xfc  0x02    
    200.2.1.4/32      13         23.0.2.3         0x03/0xfc  0x02    
    200.2.1.4/32      13         23:0:2::3        0x03/0xfc  0x02    
Processed 6 prefixes, 10 paths 
                           			
                           			
                           The following example shows a brief summary of the prefixes for all BMP modes and all AFI:
Router#show bgp bmp mode all all all table 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
BMP prefix table version : 14 
Number of RDs: 3, prefixes: 6, paths: 10 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
Route Distinguisher: 2:100 (default for vrf foo), Version 6 
   200.1.1.1/32       5          12.100.0.1       0x03/0xfc  0x00    
   200.2.1.1/32       6          12.100.0.1       0x03/0xfc  0x00    
Route Distinguisher: 2:101 (default for vrf bar), Version 8 
   200.1.1.1/32       7          12.101.0.1       0x03/0xfc  0x00    
   200.2.1.1/32       8          12.101.0.1       0x03/0xfc  0x00    
Route Distinguisher: 2:200, Version 14 
   200.1.1.4/32       14         23.0.1.3         0x03/0xfc  0x02    
    200.1.1.4/32      14         23.0.2.3         0x03/0xfc  0x02    
    200.1.1.4/32      14         23:0:2::3        0x03/0xfc  0x02    
   200.2.1.4/32       13         23.0.1.3         0x03/0xfc  0x02    
    200.2.1.4/32      13         23.0.2.3         0x03/0xfc  0x02    
    200.2.1.4/32      13         23:0:2::3        0x03/0xfc  0x02    
Processed 6 prefixes, 10 paths 
Address-Family : VPNv6 Unicast 
------------------------------------ 
BMP prefix table version : 16 
Number of RDs: 3, prefixes: 6, paths: 12 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
Route Distinguisher: 2:100 (default for vrf foo), Version 8 
   200:1:1::1/128     7          12.100.0.1       0x03/0xfc  0x00    
    200:1:1::1/128    7          12:100::1        0x03/0xfc  0x00    
   200:2:1::1/128     8          12.100.0.1       0x03/0xfc  0x00    
    200:2:1::1/128    8          12:100::1        0x03/0xfc  0x00    
Route Distinguisher: 2:101 (default for vrf bar), Version 10 
   200:1:1::1/128     9          12.101.0.1       0x03/0xfc  0x00    
   200:2:1::1/128     10         12.101.0.1       0x03/0xfc  0x00    
Route Distinguisher: 2:200, Version 16 
   200:1:1::4/128     16         23.0.2.3         0x03/0xfc  0x02    
    200:1:1::4/128    16         23:0:2::3        0x03/0xfc  0x02    
    200:1:1::4/128    16         23.0.1.3         0x03/0xfc  0x02    
   200:2:1::4/128     15         23.0.2.3         0x03/0xfc  0x02    
    200:2:1::4/128    15         23:0:2::3        0x03/0xfc  0x02    
    200:2:1::4/128    15         23.0.1.3         0x03/0xfc  0x02    
Processed 6 prefixes, 12 paths 
Address-Family : IPv4 Labeled-unicast 
------------------------------------ 
BMP prefix table version : 11 
Number of prefixes: 5, paths: 9 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
   100.1.3.3/32       10         23.0.2.3         0x03/0xfc  0x03   1 
    100.1.3.3/32      10         23.0.1.3         0x03/0xfc  0x03   1 
Processed 1 prefixes, 2 paths 
Address-Family : IPv6 Labeled-unicast 
------------------------------------ 
BMP prefix table version : 12 
Number of prefixes: 5, paths: 10 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
   100:1:3::3/128     12         23:0:2::3        0x03/0xfc  0x03   1 
    100:1:3::3/128    12         23.0.2.3         0x03/0xfc  0x03   1 
    100:1:3::3/128    12         23.0.1.3         0x03/0xfc  0x03   1 
Processed 1 prefixes, 3 paths 
Address-Family : IPv4 Unicast 
------------------------------------ 
BMP prefix table version : 11 
Number of prefixes: 5, paths: 9  
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
   100.1.1.3/32       7          23.0.1.3         0x03/0xfc  0x02   1 
   100.1.2.3/32       11         23:0:2::3        0x03/0xfc  0x02   1 
    100.1.2.3/32      11         23.0.2.3         0x03/0xfc  0x02   1 
   100.1.3.3/32       10         23.0.2.3         0x03/0xfc  0x03   1 
    100.1.3.3/32      10         23.0.1.3         0x03/0xfc  0x03   1 
   200.1.1.1/32       5          12::1            0x03/0xfc  0x00    
    200.1.1.1/32      5          12.0.0.1         0x03/0xfc  0x00    
   200.2.1.1/32       6          12::1            0x03/0xfc  0x00    
    200.2.1.1/32      6          12.0.0.1         0x03/0xfc  0x00     
Processed 5 prefixes, 9 paths 
Address-Family : IPv6 Unicast 
------------------------------------ 
BMP prefix table version : 12 
Number of prefixes: 5, paths: 10 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
   100:1:1::3/128     8          23.0.1.3         0x03/0xfc  0x02   1 
   100:1:2::3/128     9          23:0:2::3        0x03/0xfc  0x02   1 
    100:1:2::3/128    9          23.0.2.3         0x03/0xfc  0x02   1 
   100:1:3::3/128     12         23:0:2::3        0x03/0xfc  0x03   1 
    100:1:3::3/128    12         23.0.2.3         0x03/0xfc  0x03   1 
    100:1:3::3/128    12         23.0.1.3         0x03/0xfc  0x03   1 
   200:1:1::1/128     5          12.0.0.1         0x03/0xfc  0x00    
    200:1:1::1/128    5          12::1            0x03/0xfc  0x00    
   200:2:1::1/128     6          12.0.0.1         0x03/0xfc  0x00    
    200:2:1::1/128    6          12::1            0x03/0xfc  0x00    
Processed 5 prefixes, 10 paths 
---------------------------------------------- 
Route monitoring mode : Local-RIB 
----------------------------------------------
Address-Family : VPNv4 Unicast 
------------------------------------ 
BGP main routing table version : 33 
Number of prefixes: 10, paths: 10 
   Network            Next Hop            Metric LocPrf Path 
Route Distinguisher: 2:100 (default for vrf foo), Version 33 
   200.1.1.1/32       12.100.0.1               0        1 ? 
   200.1.1.4/32       23.0.1.3                 0    100 3 ? 
   200.2.1.1/32       12.100.0.1               0        1 ? 
   200.2.1.4/32       23.0.1.3                 0    100 3 ? 
Route Distinguisher: 2:101 (default for vrf bar), Version 31 
   200.1.1.1/32       12.101.0.1               0        1 ? 
   200.1.1.4/32       23.0.1.3                 0    100 3 ? 
   200.2.1.1/32       12.101.0.1               0        1 ? 
   200.2.1.4/32       23.0.1.3                 0    100 3 ? 
Route Distinguisher: 2:200, Version 27 
   200.1.1.4/32       23.0.1.3                 0    100 3 ? 
   200.2.1.4/32       23.0.1.3                 0    100 3 ? 
Processed 10 prefixes, 10 paths 
Address-Family : VPNv6 Unicast 
------------------------------------ 
BGP main routing table version : 31 
Number of prefixes: 10, paths: 10 
   Network            Next Hop            Metric LocPrf Path 
Route Distinguisher: 2:100 (default for vrf foo), Version 29 
   200:1:1::1/128     12:100::1                0        1 ? 
   200:1:1::4/128     23.0.1.3                 0    100 3 ? 
   200:2:1::1/128     12:100::1                0        1 ? 
   200:2:1::4/128     23.0.1.3                 0    100 3 ? 
Route Distinguisher: 2:101 (default for vrf bar), Version 23 
   200:1:1::1/128     12:101::1                0        1 ? 
   200:1:1::4/128     23.0.1.3                 0    100 3 ? 
   200:2:1::1/128     12:101::1                0        1 ? 
   200:2:1::4/128     23.0.1.3                 0    100 3 ? 
Route Distinguisher: 2:200, Version 31 
   200:1:1::4/128     23.0.1.3                 0    100 3 ? 
   200:2:1::4/128     23.0.1.3                 0    100 3 ? 
Processed 10 prefixes, 10 paths 
Address-Family : IPv4 Labeled-unicast 
------------------------------------ 
BGP main routing table version : 9 
Number of prefixes: 1, paths: 1 
   Network            Next Hop            Metric LocPrf Path 
   100.1.3.3/32       23.0.1.3                 0    100 ? 
Processed 1 prefixes, 1 paths 
Address-Family : IPv6 Labeled-unicast 
------------------------------------ 
BGP main routing table version : 9 
Number of prefixes: 1, paths: 1 
   Network            Next Hop            Metric LocPrf Path 
   100:1:3::3/128     23.0.1.3                 0    100 ? 
Processed 1 prefixes, 1 paths 
Address-Family : IPv4 Unicast 
------------------------------------ 
BGP main routing table version : 9 
Number of prefixes: 4, paths: 4 
   Network            Next Hop            Metric LocPrf Path 
   100.1.1.3/32       23.0.1.3                 0    100 ? 
   100.1.2.3/32       23.0.2.3                 0    100 ? 
   200.1.1.1/32       12.0.0.1                 0        1 ? 
   200.2.1.1/32       12.0.0.1                 0        1 ? 
Processed 4 prefixes, 4 paths 
Address-Family : IPv6 Unicast 
------------------------------------ 
BGP main routing table version : 9 
Number of prefixes: 4, paths: 4 
   Network            Next Hop            Metric LocPrf Path 
   100:1:1::3/128     23:0:1::3                0    100 ? 
   100:1:2::3/128     23:0:2::3                0    100 ? 
   200:1:1::1/128     12::1                    0        1 ? 
   200:2:1::1/128     12::1                    0        1 ? 
Processed 4 prefixes, 4 paths 
                           			
                           			
                           
                              
                                 |  
 Note | Specifying AFI and SAFI after the table keyword option is not supported from Release 7.5.4. So, you can specify the same before the table keyword as follows:
 show bgp bmp [mode <bmp-mode>] [<afi> <safi>] table 
 The option to specify AFIs and SAFIs after the table keyword is completely removed from Cisco IOS XR Release 24.1.1.
                                        
 | 
                           
                           			
                           The tables for VPN AFI can be filtered on a Route Distinguisher (RD) or a VRF. The following example shows the table for VPNv4 Unicast without RD or VRF filter.
Router#show bgp bmp vpnv4 unicast table  
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : VPNv4 Unicast
------------------------------------ 
BMP prefix table version : 18 
Number of RDs: 3, prefixes: 6, paths: 12 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
Route Distinguisher: 2:100 (default for vrf foo), Version 14 
   200.1.1.1/32       13         12.100.0.1       0x03/0xfc  0x02    
   200.2.1.1/32       14         12.100.0.1       0x03/0xfc  0x02    
Route Distinguisher: 2:101 (default for vrf bar), Version 16 
   200.1.1.1/32       15         12.101.0.1       0x03/0xfc  0x02    
   200.2.1.1/32       16         12.101.0.1       0x03/0xfc  0x02    
Route Distinguisher: 2:200, Version 18 
   200.1.1.4/32       17         23.0.3.3         0x03/0xfc  0x00    
    200.1.1.4/32      17         23.0.2.3         0x03/0xfc  0x00    
    200.1.1.4/32      17         23.0.4.3         0x03/0xfc  0x00    
    200.1.1.4/32      17         23.0.1.3         0x03/0xfc  0x00    
   200.2.1.4/32       18         23.0.3.3         0x03/0xfc  0x00    
    200.2.1.4/32      18         23.0.2.3         0x03/0xfc  0x00    
    200.2.1.4/32      18         23.0.4.3         0x03/0xfc  0x00    
    200.2.1.4/32      18         23.0.1.3         0x03/0xfc  0x00    
                           			
                           The following example shows the show bgp bmp vpnv4 unicast table  filtered on route distinguisher 2:100:
Router#show bgp bmp vpnv4 unicast table rd 2:100 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
BMP prefix table version : 18 
Number of RDs: 3, prefixes: 6, paths: 12 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
Route Distinguisher: 2:100 (default for vrf foo), Version 14 
   200.1.1.1/32       13         12.100.0.1       0x03/0xfc  0x02    
   200.2.1.1/32       14         12.100.0.1       0x03/0xfc  0x02    
Processed 2 prefixes, 2 paths 
                           			
                           The following example shows the show bgp bmp vpnv4 unicast table  filtered on VRF foo: 
Router#show bgp bmp vpnv4 unicast table vrf foo  
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
BMP prefix table version : 18 
Number of RDs: 3, prefixes: 6, paths: 12 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
Route Distinguisher: 2:100 (default for vrf foo), Version 14 
   200.1.1.1/32       13         12.100.0.1       0x03/0xfc  0x02    
   200.2.1.1/32       14         12.100.0.1       0x03/0xfc  0x02    
Processed 2 prefixes, 2 paths 
 
                           			
                           When the show bgp bmp table  command is run with prefix filter, it displays the details of the specified prefix as shown in the following example:
Router#show bgp bmp table 100.1.1.3/32  
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
BGP routing table entry for 100.1.1.3/32 
Versions: 
  Process           Net 
  Speaker           7           
Last Modified: Dec 16 15:05:22.000 for 07:05:14 
    Flags: 0x00000000+0x00000000 
    Net Ptr: 0x7f0bbd65ff34 
Paths: (1 available) 
  Path #1: Received by speaker 0 
  Flags: 0x00000000 
  Local 
  from 23.0.1.3 
  Nexthop: 23.0.1.3 
  Received Path ID: 1 
  Received Local Preference: 100 
  Path Advertised to BMP server(s) - (Map: 0x03): Server ID: 1, 2 
  Path pending send to BMP server(s) - (Map: 0xfc): Server ID: None 
  Path Ptr : 0x7f0bb806f0d0, BGP Path Ptr : 0x7f0bbd915f68 
 
                           			
                           The following examples displays the output of the show bgp bmp table  command with the summary keyword. It displays the summary of the table of the specified AFI or SAFI, or the default AFI or SAFI if not specified in
                              the command. 
Router#show bgp bmp table summary      
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
BMP prefix table version : 12 
Number of prefixes: 6, paths: 6
                           			
                           The following examples displays the output when you run the show bgp bmp table  command with the neighbor filter. It displays the prefixes leanrt from the specified neighbor. 
Router#show bgp bmp table neighbor 23.0.2.3 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
BMP prefix table version : 11 
Number of prefixes: 5, paths: 9 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
   100.1.2.3/32       11         23.0.2.3         0x03/0xfc  0x02   1 
   100.1.3.3/32       10         23.0.2.3         0x03/0xfc  0x03   1 
 
                           			
                           The following example displays filtering of prefixes based on prefix version range. Only the prefixes with version within
                              the specified range are displayed. 
Router#show bgp bmp table version begin 7 end 15 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
BMP prefix table version : 11 
Number of prefixes: 5, paths: 9 
   Network            Version    Neighbor         Bit Map    Flags  Path ID 
   100.1.1.3/32       7          23.0.1.3         0x03/0xfc  0x02   1 
   100.1.2.3/32       11         23:0:2::3        0x03/0xfc  0x02   1 
    100.1.2.3/32      11         23.0.2.3         0x03/0xfc  0x02   1 
   100.1.3.3/32       10         23.0.2.3         0x03/0xfc  0x03   1 
    100.1.3.3/32      10         23.0.1.3         0x03/0xfc  0x03   1 
Processed 3 prefixes, 5 paths 
                           			
                           The command show bgp bmp convergence  displays whether there is any pending work for BMP to perform and whether a specific address family has reached convergence.
                              The command is applicable to Inbound Post-Policy as well as Local-RIB modes. Convergence is declared when the following conditions are met. 
                           
                           			
                           
                              				
                              - 
                                 					
                                 Table copy is not pending (applicable only for Inbound Post-Policy) 
                                  
- 
                                 					
                                 Update generation is not pending  
- 
                                 					
                                 All BMP servers that are not administratively shutdown are Up state 
                                  
- 
                                 					
                                 All BMP servers have caught up to the table version  
- 
                                 					
                                 Write queues of all BMP servers are empty  
Router#show bgp bmp convergence  
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown.
BMP write queue is empty. 
                              			
                           			
                           The following example displays an address family that is converged. Since BMP mode is not specified, convergence details are
                              shown for the default mode inbound post-policy. 
Router#show bgp bmp vpnv4 unicast convergence  
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           The following example displays the convergence details for all AFIs and SAFIs. Since BMP mode is not specified, convergence
                              information is shown for the default mode inbound post-policy. 
Router#show bgp bmp all all convergence       
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : VPNv6 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv4 Labeled-unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv6 Labeled-unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv6 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           The following example displays the convergence details for BMP mode inbound post-policy  explicitly specified. The output of this command is same as that of show bgp bmp mode convergence  as the explicitly specified mode is same as the default mode. 
Router#show bgp bmp mode inbound post-policy convergence  
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           The following examples displays the convergence details for BMP Local-RIB. 
Router#show bgp bmp mode local-rib convergence            
---------------------------------------------- 
Route monitoring mode : Local-RIB 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           The following examples displays the convergence details for non-default address family VPNv4 Unicast. 
Router#show bgp bmp mode local-rib vpnv4 unicast convergence  
---------------------------------------------- 
Route monitoring mode : Local-RIB 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           The following examples displays the convergence details for all address families for BMP mode Local-RIB. 
Router#show bgp bmp mode local-rib all all convergence 
---------------------------------------------- 
Route monitoring mode : Local-RIB 
---------------------------------------------- 
Address-Family : VPNv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : VPNv6 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv4 Labeled-unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv6 Labeled-unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
Address-Family : IPv6 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           The following example shows the convergence details of an address family that has not converged (in this case the default
                              address family ipv4 unicast since it is not specified in the command). In this example, in case of Inbound Post-Policy, convergence is not reached as the servers are in Down state and they have not caught up to the Table version:
Router#show bgp bmp mode all convergence 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Not converged. 
All paths from monitored neighbors may not be sent to the BMP servers that are not administratively shutdown. 
Table copy pending: N 
Update generation pending: N 
Table version: 108 
Server  Caught-Up Version  Queue Size  State 
------------------------------------------------- 
      1                  0           0  Down 
      2                  0           0  Down 
---------------------------------------------- 
Route monitoring mode : Local-RIB 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Not converged. 
All paths from monitored neighbors may not be sent to the BMP servers that are not administratively shutdown. 
Table copy pending: N 
Update generation pending: N 
Table version: 28 
Server  Caught-Up Version  Queue Size  State 
------------------------------------------------- 
      1                  0           0  Down 
      2                  0           0  Down 
                           			
                           In the following example of the show bgp bmp mode all convergence  command, convergence is reached for BMP mode local-rib and address-family ipv4 unicast. However, the same is not yet reached
                              for BMP mode inbound post-policy and address-family ipv4 unicast. 
Router#show bgp bmp mode all convergence 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Not converged. 
All paths from monitored neighbors may not be sent to the BMP servers that are not administratively shutdown. 
Table copy pending: N 
Update generation pending: Y 
Table version: 108 
 Server  Caught-Up Version  Queue Size  State 
------------------------------------------------- 
      1                  0           0  Up 
      2                  0           0  Up 
---------------------------------------------- 
Route monitoring mode : Local-RIB 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           In the following example of the same command, convergence is still not reached for BMP mode inbound post-policy. In this case
                              the server are in Up state and they have caught up to the Table version. However, the queue for Server 1 is not empty. 
Router#show bgp bmp mode all convergence 
---------------------------------------------- 
Route monitoring mode : Inbound Post-Policy 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Not converged. 
All paths from monitored neighbors may not be sent to the BMP servers that are not administratively shutdown. 
Table copy pending: N 
Update generation pending: N 
Table version: 108 
Server  Caught-Up Version  Queue Size  State 
------------------------------------------------- 
      1                108         432  Up 
      2                108           0  Up 
---------------------------------------------- 
Route monitoring mode : Local-RIB 
---------------------------------------------- 
Address-Family : IPv4 Unicast 
------------------------------------ 
Converged. 
All paths from monitored neighbors are sent to the BMP servers that are not administratively shutdown. 
BMP write queue is empty. 
                           			
                           
                              				
                              
                                 
                                    |  
 Note | 
 The origin of prefixes conveyed in the Inbound Post-Policy view conveys is the actual BGP peers. Whereas the origin of prefixes conveyed in the Local-RIB view is the Local-RIB itself. The Local-RIB is viewed as a set of emulated peers from which the prefixes originate. Each emulated peer is associated with the prefixes belonging to one VRF (all address
                                             families inclusive) that are conveyed to one BMP server. In other words, one emulated peer is per-VRF per-BMP server. So,
                                             if BGP has n VRFs and there are m BMP servers, then n x m emulated peers are created automatically.
                                           The internal construct of the emulated peer is largely same as that of the normal BGP peer. So, the output of some of the
                                             emulated peers related commands resembles that of the BGP peer related commands. 
                                           
 | 
                              
                              			
                           
                           			
                           The following example shows the details of the Local RIB emulated peers. 
                           			
                           
                              
                                 |  
 Note | 
 This keyword emulated-peers is applicable only to BMP mode Local RIB.
                                        
 | 
                           
                           			
                           
                              				
Router#show bgp bmp mode local-rib emulated-peers 
BGP emulated peer is 0.0.0.1 
Remote AS 2, local AS 2, internal link 
Remote router ID 100.1.1.2 
  BGP state = Established, up for 08:05:38 
  Previous State: Idle 
  Last Received Message: None 
  BGP Monitoring(BMP) activated for servers:  
      1 
  Multi-protocol capability received 
  Emulated peer capabilities: 
    Route refresh: advertised (old + new) 
    4-byte AS: advertised and received 
    Address family IPv4 Unicast: advertised and received 
    Address family IPv4 Labeled-unicast: advertised and received 
    Address family VPNv4 Unicast: advertised and received 
    Address family IPv6 Unicast: advertised and received 
    Address family IPv6 Labeled-unicast: advertised and received 
    Address family VPNv6 Unicast: advertised and received 
  Received 0 messages, 0 notifications, 0 in queue 
  Sent 20 messages, 0 notifications, 0 in queue 
  Minimum time between advertisement runs is 15 secs 
For Address Family: IPv4 Unicast 
  BMP emulated peer version 9 
  Update group: 0.9 Filter-group: 0.8  No Refresh request being processed 
  Route-Reflector Client 
    Extended Nexthop Encoding: advertised and received 
  Route refresh request: received 0, sent 0 
  Prefix advertised 4, suppressed 0, withdrawn 0 
  AIGP is enabled 
  Last ack version 9, Last synced ack version 0 
  Outstanding version objects: current 0, max 1, refresh 0 
  Additional-paths operation: None 
  Send Multicast Attributes 
  Advertise routes with local-label via Unicast SAFI 
For Address Family: IPv4 Labeled-unicast 
  BMP emulated peer version 9 
  Update group: 0.10 Filter-group: 0.9  No Refresh request being processed 
  Route-Reflector Client 
    Extended Nexthop Encoding: advertised and received 
  Route refresh request: received 0, sent 0 
  Prefix advertised 1, suppressed 0, withdrawn 0 
  AIGP is enabled 
  Last ack version 9, Last synced ack version 0 
  Outstanding version objects: current 0, max 1, refresh 0 
  Additional-paths operation: None 
  Send Multicast Attributes 
For Address Family: VPNv4 Unicast 
  BMP emulated peer version 33 
  Update group: 0.7 Filter-group: 0.6  No Refresh request being processed 
  Route-Reflector Client 
    Extended Nexthop Encoding: advertised and received 
  Route refresh request: received 0, sent 0 
  Prefix advertised 6, suppressed 0, withdrawn 0 
  AIGP is enabled 
  Last ack version 33, Last synced ack version 0 
  Outstanding version objects: current 0, max 1, refresh 0 
  Additional-paths operation: None 
  Send Multicast Attributes 
For Address Family: IPv6 Unicast 
  BMP emulated peer version 9 
  Update group: 0.11 Filter-group: 0.9  No Refresh request being processed 
  Route-Reflector Client 
    Extended Nexthop Encoding: advertised and received 
  Route refresh request: received 0, sent 0 
  Prefix advertised 4, suppressed 0, withdrawn 0 
  AIGP is enabled 
  Last ack version 9, Last synced ack version 0 
  Outstanding version objects: current 0, max 1, refresh 0 
  Additional-paths operation: None 
  Send Multicast Attributes 
  Advertise routes with local-label via Unicast SAFI 
For Address Family: IPv6 Labeled-unicast 
  BMP emulated peer version 9 
  Update group: 0.12 Filter-group: 0.10  No Refresh request being processed 
  Route-Reflector Client 
    Extended Nexthop Encoding: advertised and received 
  Route refresh request: received 0, sent 0 
  Prefix advertised 1, suppressed 0, withdrawn 0 
  AIGP is enabled 
  Last ack version 9, Last synced ack version 0 
  Outstanding version objects: current 0, max 1, refresh 0 
  Additional-paths operation: None 
  Send Multicast Attributes 
For Address Family: VPNv6 Unicast 
  BMP emulated peer version 31 
  Update group: 0.7 Filter-group: 0.6  No Refresh request being processed 
  Route-Reflector Client 
    Extended Nexthop Encoding: advertised and received 
  Route refresh request: received 0, sent 0 
  Prefix advertised 6, suppressed 0, withdrawn 0 
  AIGP is enabled 
  Last ack version 31, Last synced ack version 0 
  Outstanding version objects: current 0, max 1, refresh 0 
  Additional-paths operation: None 
  Send Multicast Attributes 
  Connections established 1; dropped 0 
  Last reset 00:00:00 
                              			
                           			
                           The show bgp bmp mode local-rib emulated peers  command with additional keyword brief is used to display a brief summary of the Local RIB emulated peers. 
Router#show bgp bmp mode local-rib emulated-peers brief 
EmuPeerId       BMPServer  VRF                   Spk    AS  OutQ  State 
0.0.0.1                 1  default                 0     2     0  Established 
0.0.0.2                 2  default                 0     2     0  Established 
0.0.0.1                 1  bar                     0     2     0  Established 
0.0.0.2                 2  bar                     0     2     0  Established 
0.0.0.1                 1  foo                     0     2     0  Established 
0.0.0.2                 2  foo                     0     2     0  Established 
                           			
                           The following example shows the detailed summary about Local RIB emulated peers when the detail keyword is used. 
Router#show bgp bmp mode local-rib emulated-peers detail  
BGP emulated peer is 0.0.0.1 
 Remote AS 2, local AS 2, internal link 
 Remote router ID 100.1.1.2 
  BGP state = Established, up for 2d20h 
  Previous State: Idle 
  Last Received Message: None 
  BGP Monitoring(BMP) activated for servers:  
      1 
  Multi-protocol capability received 
  Emulated peer capabilities:       Adv         Rcvd 
    Route refresh:                  Yes         No 
    4-byte AS:                      Yes         Yes 
    Address family IPv4 Unicast:    Yes         Yes 
    Address family IPv4 Labeled-unicast:  Yes         Yes 
    Address family VPNv4 Unicast:   Yes         Yes 
    Address family IPv6 Unicast:    Yes         Yes 
    Address family IPv6 Labeled-unicast:  Yes         Yes 
    Address family VPNv6 Unicast:   Yes         Yes 
  Message stats: 
    OutQ depth: 0 
  Minimum time between advertisement runs is 15 secs 
                           			
                           The following example shows the detailed summary of a Local RIB emulated peer specified by VRF and emulated-peer address. 
Router#show bgp bmp mode local-rib vrf foo emulated-peers 0.0.0.1 detail  
BGP emulated peer is 0.0.0.1, vrf foo 
 Remote AS 2, local AS 2, internal link 
 Remote router ID 100.1.1.2 
  BGP state = Established, up for 2d21h 
  Previous State: Idle 
  Last Received Message: None 
  BGP Monitoring(BMP) activated for servers:  
      1 
  Multi-protocol capability received 
  Emulated peer capabilities:       Adv         Rcvd 
    Route refresh:                  Yes         No 
    4-byte AS:                      Yes         Yes 
    Address family IPv4 Unicast:    Yes         Yes 
    Address family IPv6 Unicast:    Yes         Yes 
  Message stats: 
    OutQ depth: 0 
  Minimum time between advertisement runs is 15 secs
                           			
                           The following example shows the performance statistics information of a Local RIB emulated peer specified with VRF and emulated-peer address. 
Router#show bgp bmp mode local-rib vrf foo emulated-peers 0.0.0.1 performance-statistics 
BGP neighbor is 0.0.0.1, vrf foo 
 Remote AS 2 
  Read 0 messages (0 bytes) in 0 calls (time spent: 0.000 secs) 
  Read partly throttled 0 times 
  Max socket read size: 0 bytes 
  Processed 0 inbound update messages (time spent: 0.000 secs) 
  Wrote 750 bytes in 2 calls (time spent: 0.000 secs) 
  Processing sub-group: wrote 6 messages in 4 calls (time spent: 0.000 secs) 
  Processing write queue: wrote 0 messages in 0 calls (time spent: 0.000 secs) 
  Received 0 messages, 0 notifications, 0 in queue 
  Sent 6 messages, 0 notifications, 0 in queue 
  NSR State: None 
  Nbr Primary fd:-1 Reset flags:0x0 Sync flags:0x0 Nbr-flags:0x3000c0 Rst retries:0 
 For Address Family: IPv4 Unicast 
  Message statistics: 
    Update messages processed: 3 
    Update messages sent: 3 
    Split-horizon Advertisement messages: sent 0, blocked 0 
    Split-horizon Withdraw messages: sent 0, blocked 0 
 For Address Family: IPv6 Unicast 
  Message statistics: 
    Update messages processed: 3 
    Update messages sent: 3 
    Split-horizon Advertisement messages: sent 0, blocked 0 
    Split-horizon Withdraw messages: sent 0, blocked 0 
                           			
                           The following example displays the details of all emulated peers belonging to all VRFs. 
Router#show bgp bmp mode local-rib vrf all emulated-peers  
VRF: bar 
-------- 
BGP emulated peer is 0.0.0.1, vrf bar 
 Remote AS 2, local AS 2, internal link 
 Remote router ID 100.1.1.2 
  BGP state = Established, up for 2d22h 
  Previous State: Idle 
  Last Received Message: None 
  BGP Monitoring(BMP) activated for servers:  
      1 
  Multi-protocol capability received 
  Emulated peer capabilities: 
    Route refresh: advertised (old + new) 
    4-byte AS: advertised and received 
    Address family IPv4 Unicast: advertised and received 
    Address family IPv6 Unicast: advertised and received 
  Received 0 messages, 0 notifications, 0 in queue 
  Sent 6 messages, 0 notifications, 0 in queue 
  Minimum time between advertisement runs is 15 secs 
 For Address Family: IPv4 Unicast 
  BMP emulated peer version 25 
  Update group: 0.1 Filter-group: 0.3  No Refresh request being processed 
  Route-Reflector Client 
                           			
                           The following example displays the details of all emulated peers belong to a specified VRF. 
Router#show bgp bmp mode local-rib vrf foo emulated-peers  
BGP emulated peer is 0.0.0.1, vrf foo 
 Remote AS 2, local AS 2, internal link 
 Remote router ID 100.1.1.2 
  BGP state = Established, up for 2d22h 
  Previous State: Idle 
  Last Received Message: None 
  BGP Monitoring(BMP) activated for servers:  
      1 
  Multi-protocol capability received 
  Emulated peer capabilities: 
    Route refresh: advertised (old + new) 
    4-byte AS: advertised and received 
    Address family IPv4 Unicast: advertised and received 
    Address family IPv6 Unicast: advertised and received 
  Received 0 messages, 0 notifications, 0 in queue 
  Sent 6 messages, 0 notifications, 0 in queue 
  Minimum time between advertisement runs is 15 secs 
 For Address Family: IPv4 Unicast 
  BMP emulated peer version 25 
  Update group: 0.1 Filter-group: 0.3  No Refresh request being processed 
  Route-Reflector Client