diff options
| author | ISHIDA Wataru <ishida.wataru@lab.ntt.co.jp> | 2016-01-08 14:09:27 +0900 |
|---|---|---|
| committer | FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | 2016-01-09 05:17:57 -0800 |
| commit | da01fa48af05820d8b8731379cf647be049be503 (patch) | |
| tree | 5c804613de7f1602bf2a3eba4cf876abf7a1ecdc /docs/sources/cli-operations.md | |
| parent | 6ee7c63eb36412903476b6b14e6ec83b6fe5f1ba (diff) | |
docs: update
Signed-off-by: ISHIDA Wataru <ishida.wataru@lab.ntt.co.jp>
Diffstat (limited to 'docs/sources/cli-operations.md')
| -rw-r--r-- | docs/sources/cli-operations.md | 67 |
1 files changed, 31 insertions, 36 deletions
diff --git a/docs/sources/cli-operations.md b/docs/sources/cli-operations.md index dd1cc560..48f373b3 100644 --- a/docs/sources/cli-operations.md +++ b/docs/sources/cli-operations.md @@ -12,7 +12,7 @@ This example starts with the same configuration with [Getting Started](https://g Make sure that all the peers are connected. -``` +```bash $ gobgp neighbor Peer AS Up/Down State |#Advertised Received Accepted 10.0.255.1 65001 00:00:04 Establ | 2 2 2 @@ -29,41 +29,36 @@ file and sending `HUP` signal to GoBGP daemon. In this example, 10.0.255.3 peer is added. The configuration file should be like the following. -``` -[Global] - [Global.Config] - As = 64512 - RouterId = "192.168.255.1" - -[Neighbors] - [[Neighbors.NeighborList]] - [Neighbors.NeighborList.Config] - NeighborAddress = "10.0.255.1" - PeerAs = 65001 - [Neighbors.NeighborList.RouteServer] - [Neighbors.NeighborList.RouteServer.Config] - RouteServerClient = true - - [[Neighbors.NeighborList]] - [Neighbors.NeighborList.Config] - NeighborAddress = "10.0.255.2" - PeerAs = 65002 - [Neighbors.NeighborList.RouteServer] - [Neighbors.NeighborList.RouteServer.Config] - RouteServerClient = true - - [[Neighbors.NeighborList]] - [Neighbors.NeighborList.Config] - NeighborAddress = "10.0.255.3" - PeerAs = 65003 - [Neighbors.NeighborList.RouteServer] - [Neighbors.NeighborList.RouteServer.Config] - RouteServerClient = true +```toml +[global.config] + as = 64512 + router-id = "192.168.255.1" + +[[neighbors]] +[neighbors.config] + neighbor-address = "10.0.255.1" + peer-as = 65001 +[neighbors.route-server.config] + route-server-client = true + +[[neighbors]] +[neighbors.config] + neighbor-address = "10.0.255.2" + peer-as = 65002 +[neighbors.route-server.config] + route-server-client = true + +[[neighbors]] +[neighbors.config] + neighbor-address = "10.0.255.3" + peer-as = 65003 +[neighbors.route-server.config] + route-server-client = true ``` After you send `HUP` signal (`kill` command), you should see 10.0.255.3 peer. -``` +```bash $ gobgp neighbor Peer AS Up/Down State |#Advertised Received Accepted 10.0.255.1 65001 00:03:42 Establ | 3 2 2 @@ -77,7 +72,7 @@ Sometime you might want to disable the configured peer without removing the configuration for the peer. Likely, again you enable the peer later. -``` +```bash $ gobgp neighbor 10.0.255.1 disable $ gobgp neighbor Peer AS Up/Down State |#Advertised Received Accepted @@ -88,7 +83,7 @@ Peer AS Up/Down State |#Advertised Received Accepted The state of 10.0.255.1 is `Idle(Admin)`. Let's enable the peer again. -``` +```bash $ gobgp neighbor 10.0.255.1 enable $ gobgp neighbor Peer AS Up/Down State |#Advertised Received Accepted @@ -99,7 +94,7 @@ Peer AS Up/Down State |#Advertised Received Accepted Eventually, the state should be `Established` again. -``` +```bash $ gobgp neighbor Peer AS Up/Down State |#Advertised Received Accepted 10.0.255.1 65001 00:00:02 Establ | 3 2 2 @@ -111,7 +106,7 @@ Peer AS Up/Down State |#Advertised Received Accepted Various reset operations are supported. -``` +```bash $ gobgp neighbor 10.0.255.1 reset $ gobgp neighbor 10.0.255.1 softreset $ gobgp neighbor 10.0.255.1 softresetin |