mirror/osrg-gobgp
1
0
Fork 0
mirror of https://github.com/osrg/gobgp.git synced 2024-05-11 05:55:10 +00:00
Code Issues Releases Activity

docs: update all the docs about the new CLI syntax

Browse Source 
Signed-off-by: FUJITA Tomonori <[email protected]>
This commit is contained in:
FUJITA Tomonori
2015-04-22 21:19:46 +09:00
parent cd31ffea16
commit c8fdac2ee5
3 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/filter.md
+3 -3
View File
@@ -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}]
docs/sources/getting-started.md
+4 -4
View File
@@ -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]}]
```
docs/sources/route-server.md
+2 -2
View File
@@ -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}]