diff options
| -rw-r--r-- | docs/sources/filter.md | 6 | ||||
| -rw-r--r-- | docs/sources/getting-started.md | 8 | ||||
| -rw-r--r-- | docs/sources/route-server.md | 4 |
3 files changed, 9 insertions, 9 deletions
diff --git a/docs/sources/filter.md b/docs/sources/filter.md index 041a9be0..7e186f95 100644 --- a/docs/sources/filter.md +++ b/docs/sources/filter.md @@ -92,7 +92,7 @@ If the *pd2* sets *MatchSetOptions* to 0, any of match conditions meets, the pol Confirm that 10.0.255.1 neighbor advertises two routes. ``` -$ gobgp show neighbor 10.0.255.1 adj-in +$ gobgp neighbor 10.0.255.1 adj-in Network Next Hop AS_PATH Age Attrs 10.3.0.0/16 10.0.255.1 [65001] 00:51:57 [{Origin: 0} {Med: 0}] 10.33.0.0/16 10.0.255.1 [65001] 00:51:57 [{Origin: 0} {Med: 0}] @@ -101,10 +101,10 @@ $ gobgp show neighbor 10.0.255.1 adj-in Now let's check out if the policy works as expected. ``` -$ gobgp show neighbor 10.0.255.2 local +$ gobgp neighbor 10.0.255.2 local Network Next Hop AS_PATH Age Attrs *> 10.3.0.0/16 10.0.255.1 [65001] 00:49:36 [{Origin: 0} {Med: 0}] -$ gobgp show neighbor 10.0.255.3 local +$ gobgp neighbor 10.0.255.3 local Network Next Hop AS_PATH Age Attrs *> 10.3.0.0/16 10.0.255.1 [65001] 00:49:38 [{Origin: 0} {Med: 0}] *> 10.33.0.0/16 10.0.255.1 [65001] 00:49:38 [{Origin: 0} {Med: 0}] diff --git a/docs/sources/getting-started.md b/docs/sources/getting-started.md index a0e7587d..f105b21f 100644 --- a/docs/sources/getting-started.md +++ b/docs/sources/getting-started.md @@ -59,7 +59,7 @@ $ sudo -E gobgpd -f gobgpd.conf Let's show the information of all the peers. ``` -$ gobgp show neighbors +$ gobgp neighbor Peer AS Up/Down State |#Advertised Received Accepted 10.0.255.1 65001 00:00:14 Establ | 1 5 5 10.0.255.2 65002 00:00:14 Establ | 5 2 2 @@ -68,7 +68,7 @@ Peer AS Up/Down State |#Advertised Received Accepted Want to the details of a particular peer? ``` -$ gobgp show neighbor 10.0.255.1 +$ gobgp neighbor 10.0.255.1 BGP neighbor is 10.0.255.1, remote AS 65001 BGP version 4, remote router ID 192.168.0.1 BGP state = BGP_FSM_ESTABLISHED, up for 00:01:49 @@ -106,14 +106,14 @@ Check out the global table. You also can look at adjacent rib-in and rib-out: ``` -$ gobgp show neighbor 10.0.255.1 adj-in +$ gobgp neighbor 10.0.255.1 adj-in Network Next Hop AS_PATH Age Attrs 10.3.0.0/16 10.0.255.1 [65001] 00:06:55 [{Origin: 0} {Med: 0}] 10.3.0.0/24 10.0.255.1 [65001] 00:06:55 [{Origin: 0} {Med: 0}] 10.3.0.0/32 10.0.255.1 [65001] 00:06:55 [{Origin: 0} {Med: 0}] 10.3.0.1/32 10.0.255.1 [65001] 00:06:55 [{Origin: 0} {Med: 0}] 10.33.0.0/16 10.0.255.1 [65001] 00:06:55 [{Origin: 0} {Med: 0}] -$ gobgp show neighbor 10.0.255.1 adj-out +$ gobgp neighbor 10.0.255.1 adj-out Network Next Hop AS_PATH Attrs 192.168.2.0/24 10.0.255.254 [64512 65002] [{Origin: 0} {Cummunity: [65001:65002 NO_EXPORT]}] ``` diff --git a/docs/sources/route-server.md b/docs/sources/route-server.md index 673c9762..d3f8ed31 100644 --- a/docs/sources/route-server.md +++ b/docs/sources/route-server.md @@ -52,14 +52,14 @@ GoBGP implements multiple RIBs, that is, each peer has own local RIB. Let's check respectively. ``` -$ gobgp show neighbor 10.0.255.1 local +$ gobgp neighbor 10.0.255.1 local Network Next Hop AS_PATH Age Attrs *> 10.3.0.0/24 10.0.255.2 [65002] 00:05:50 [{Origin: 0} {Med: 0}] *> 192.168.2.0/24 10.0.255.2 [65002] 00:05:50 [{Origin: 0} {Med: 0}] ``` ``` -$ gobgp show neighbor 10.0.255.2 local +$ gobgp neighbor 10.0.255.2 local Network Next Hop AS_PATH Age Attrs *> 10.3.0.0/16 10.0.255.1 [65001] 00:06:12 [{Origin: 0} {Med: 0}] *> 10.3.0.1/32 10.0.255.1 [65001] 00:06:12 [{Origin: 0} {Med: 0}] |