create bgp peer

Ze command

Registry path

create bgp peer

Usage

create bgp peer <selector> <asn> [local-as <local-as>] [local-address <local-address>] [router-id <router-id>] [receive-hold-time <receive-hold-time>] [send-hold-time <send-hold-time>] [connect-retry <connect-retry>] [connect <true|false>] [accept <true|false>] [family <family>] [graceful-restart <graceful-restart>] [group-updates <true|false>] [attach <attach>]

Mode

Daemon

Wire method

ze-bgp:peer-add

Backends

any backend

Task support

optional: the MCP call is synchronous, which is the default

Subcommands

none: this command takes no subcommand

Pipes, always

json, ndjson, table, text, yaml, raw, no-more, save

Pipes, when the answer has rows

match, count, first, last, display, fill

Pipes, while streaming

log

Pipes, local process only

save

Description

The peer address and 'asn' are required. Every other keyword is
optional. Ze builds the peer, starts it, and dials the address unless 'connect
false' says otherwise. The peer lives in the running daemon alone. Ze writes
nothing to the configuration, so a reload removes the peer. 'delete bgp peer'
does the same on the way out, and it does not change the file on disk. An
address that already names a peer is refused, and so is a keyword Ze cannot
honor. Each name in 'attach' is bound to the whole surface: that process
receives every message from this peer and can send every type toward it. Write
the receive and send lists in the configuration file when the process needs
less.

Arguments