Dell OS10 BGP Configuration: CLI Steps and Verification

OS10 keeps its routing configuration close to the FRR syntax that many engineers already know, which makes BGP on a Dell PowerSwitch quick to learn - provided you respect OS10's transaction-based configuration model and the address-family activation step that quietly decides whether routes are exchanged at all. This guide configures eBGP and iBGP neighbours on a PowerSwitch, uses templates to keep large peer sets manageable, injects networks, and finishes with the verification commands that prove the session and the RIB are healthy.

Before BGP: the prerequisites people skip

OS10# configure terminal
OS10(config)# interface loopback0
OS10(config-if-loopback0)# ip address 10.0.0.1/32
OS10(config-if-loopback0)# exit
OS10(config)# interface ethernet1/1/1
OS10(config-if)# no switchport
OS10(config-if)# ip address 10.12.1.1/30
OS10(config-if)# exit
OS10(config)# ip route 0.0.0.0/0 10.12.1.2
OS10(config)# commit

A BGP router ID must be the IP of a configured L3 interface - a loopback is the correct choice. Confirm the interface is in routed mode (no switchport); a BGP neighbour over a switchport will never establish, and the error message gives no hint about the real cause.

eBGP and iBGP neighbours

OS10(config)# router bgp 65001
OS10(config-router-bgp-65001)# router-id 10.0.0.1
OS10(config-router-bgp-65001)# log-neighbor-changes

! external peer
OS10(config-router-bgp-65001)# neighbor 10.12.1.2
OS10(config-router-neighbor)# remote-as 65002
OS10(config-router-neighbor)# description eBGP-to-ISP
OS10(config-router-neighbor)# no shutdown
OS10(config-router-neighbor)# exit

! internal peer, update-source pinned to the loopback
OS10(config-router-bgp-65001)# neighbor 10.0.0.2
OS10(config-router-neighbor)# remote-as 65001
OS10(config-router-neighbor)# update-source loopback0
OS10(config-router-neighbor)# no shutdown
OS10(config-router-neighbor)# exit

! address family - this is what actually enables exchange
OS10(config-router-bgp-65001)# address-family ipv4 unicast
OS10(config-router-af)# neighbor 10.12.1.2 activate
OS10(config-router-af)# neighbor 10.0.0.2 activate
OS10(config-router-af)# network 10.0.0.0/24
OS10(config-router-af)# maximum-paths ebgp 4
OS10(config-router-af)# exit
OS10(config-router-bgp-65001)# exit
OS10(config)# commit

The activate statement under address-family ipv4 unicast is the step that catches everyone coming from IOS: configure the neighbour without activating it in the address family and the session comes up while carrying zero routes. In OS10, neighbor ip-address enters a per-neighbour sub-mode, so you configure one peer at a time unless you use templates.

Peer templates for larger deployments

OS10(config-router-bgp-65001)# template ISP-PEERS
OS10(config-router-template)# description "ISP facing peers"
OS10(config-router-template)# remote-as 65002
OS10(config-router-template)# timers 10 30
OS10(config-router-template)# ebgp-multihop 2
OS10(config-router-template)# address-family ipv4 unicast
OS10(config-router-af)# send-community
OS10(config-router-af)# route-map RM-IN in
OS10(config-router-af)# route-map RM-OUT out
OS10(config-router-af)# exit
OS10(config-router-template)# exit
OS10(config-router-bgp-65001)# neighbor 10.12.1.6 inherit template ISP-PEERS
OS10(config-router-bgp-65001)# exit
OS10(config)# commit

Templates keep policy consistent across many peers and make a config audit realistic: one route map referenced in one place instead of twenty. Combine with a route map that sets local preference and communities for inbound traffic engineering.

Verification

OS10# show ip bgp summary
OS10# show ip bgp neighbors 10.12.1.2
OS10# show ip bgp neighbors 10.12.1.2 advertised-routes
OS10# show ip bgp neighbors 10.12.1.2 received-routes
OS10# show ip bgp
OS10# show ip bgp 10.0.0.0/24
OS10# show running-configuration bgp
OS10# show ip route bgp
OS10# clear ip bgp *                     ! reset all sessions (be careful)
OS10# clear ip bgp 10.12.1.2 soft in      ! re-apply inbound policy only

In show ip bgp summary a healthy peer shows established in the State/Pfx column along with a prefix count. If the session is established but the prefix count is zero, the address-family activation or a route map is the problem - not connectivity. Remember that OS10 configuration is transactional: uncommitted changes exist only in the candidate configuration, so show running-configuration is the source of truth and discard throws away a session's worth of edits.

Operational notes

Keep log-neighbor-changes enabled and ship the logs off-box; pair BGP with BFD for sub-second failure detection where the peer supports it; and validate the whole change in a containerlab or lab switch first. Related reading: Dell OS10 OSPF configuration, OS10 transaction-based configuration mode, BGP best path selection and route reflectors and cluster-id.

原文链接：https://www.dell.com/support/manuals/en-cr/dell-emc-smartfabric-os10/smartfabric-os-user-guide-10-5-0/enable-bgp