-
Notifications
You must be signed in to change notification settings - Fork 2
bgp softver
Pre-Alpha. This page describes behavior that may change.
Software version capability. Advertises the Ze version string to peers in the OPEN message.
Capabilities.
plugin {
internal softver { use bgp-softver }
}
bgp {
peer upstream {
capability {
softver;
}
}
}
During OPEN negotiation, the plugin injects the Software Version capability (code 75, draft) with the build version string. Peers that receive the capability can surface the remote side's software version in their operator tools.
The capability is informational only and draft-status. Not every peer will recognise it, and not every peer will advertise it back. It is useful when you want to know which version of Ze you are peering with without asking the operator on the other side.
- Reads the Ze version string at startup (
YY.MM.DDformat based on build date).
main/internal/component/bgp/plugins/softver/
Unreviewed draft. This wiki was authored in bulk and has not been reviewed. File corrections on the issue tracker.
- Overview
- YANG Model
- Editor Workflow
- Archive and Rollback
- System
- Interfaces
- VRRP
- BFD
- FIB
- OSPF
- IS-IS
- MPLS / LDP / RSVP-TE
- RSVP-TE
- SRv6
- Static Routes
- Policy Routing
- Firewall
- Traffic Control
- Class of Service
- L2TP/PPP
- PPPoE
- VPP Data Plane
- RPKI
- IPsec VPN
- TACACS+ AAA
- RADIUS AAA
- AS112 DNS
- Authorization
- Fleet
- BGP
- Starting and Stopping
- Show Commands
- Monitoring
- Flow Export
- DDoS Mitigation
- Anomaly Detection
- Health Checks
- Audit Trail
- Production Diagnostics
- Logging
- Operational Reports
- Healthcheck
- Self-Update
- Zero-Touch Provisioning
- MRT Analysis
- Upgrade and Restart
- Storage
- Policy
- Core
- Resilience
- Validation
- Capabilities
- Address Families
- Protocol
- Subsystems
- Infrastructure
- Route Server at an IXP
- Transit Edge with RPKI
- Public Looking Glass
- ExaBGP Migration Walkthrough
- FlowSpec Injection
- Chaos-Tested Peering
- AS Path Topology