Command map

send bgp unicast

Originate a unicast route on demand.

Ze command

Registry path
send bgp unicast
Usage
send bgp <selector> unicast <prefix> [next-hop <address>] [community <value> ...] [tag <key> <value>] [for <duration>]
Mode
Daemon
Wire method
ze-bgp:announce-unicast
Backends
any backend
Task support
optional: the MCP call is synchronous, which is the default
Subcommands
community for next-hop tag
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 address family follows the prefix, so it is ipv4 unicast or ipv6
unicast. The ORIGIN is IGP, and the next hop is this router unless next-hop names one.

Arguments

NameTypeRequiredValuesSummaryDescription
selectorstringyesany value of this typePeer selectorThe value is an IP address, a peer name, an AS pattern such as as65001, a glob, a comma-separated list of those, or * for every peer. The message goes to each session the selector matches.
prefixstringyesany value of this typePrefix to originate, in CIDR formThe value is an IPv4 or IPv6 prefix with its length, such as 192.0.2.0/24. The address family of the route follows from the prefix. A value that is not a prefix is refused.

Mapping status

No vendor equivalent has been curated yet for this Ze command.

Juniper Junos MX

No equivalent is listed for this vendor yet.

Cisco IOS XR

No equivalent is listed for this vendor yet.

Nokia SR OS

No equivalent is listed for this vendor yet.

VyOS

No equivalent is listed for this vendor yet.