Diagnostic runbook from NSX ODS. Feed it a logical router together with two IP addresses and it checks how healthy Edge routing is, reads the RIB, FIB and ARP entries, and then pings and traces the path.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains EdgeRouting in context, with comparison tables and the common traps.
Terms in this definition
- Runbook
An Azure Automation job script, in PowerShell, Python or graphical form, executed in an Azure sandbox or on a Hybrid Runbook Worker; a typical example resizes a VM at scheduled times.
- NSX
Software that handles networking and security across VCF, covering firewalling, load balancing, NAT, VPCs, overlay segments and Tier-0/1 gateways.
- ODS
The On Demand Support capability in NSX that executes built-in runbooks (for instance BgpNeighborState or EdgeRouting) one step at a time, finishing each with a report and artefacts to inspect or export.
- Azure Artifacts feed
Holds packages (Cargo, Universal, Python, Maven, npm, NuGet) in Artifacts; it belongs to a project or the organisation and supports views, feed roles and upstreams.
- Logical
Independent of any implementation. Each logical design is made real through a physical counterpart.
- Geographic
A Traffic Manager routing method that picks the endpoint according to where the user is located geographically.
- RIB
Table where a router keeps the routes it has learned, used to build the forwarding information base (FIB). The EdgeRouting runbook in NSX ODS examines a logical router's RIB, FIB and ARP entries.
- FIB
Forwarding information base: the lookup table an NSX Edge compiles from its RIB. It is one of the things the EdgeRouting ODS runbook examines, and VCF Operations for networks harvests the Edge routes held in it.