Manual Chapter : Move ZebOS BGP and BFD routing configuration to tmsh

Applies To:

Show Versions Show Versions


  • 13.1.1, 13.1.0
Manual Chapter

Move ZebOS BGP and BFD routing configuration to tmsh

The same commands used in ZebOS
for BGP and BFD can be used in
with a few exceptions, as noted in the HTML files located in the downloads section on You will have to create a new deployment because migration compatibility is not yet available.
Currently BGP and BFD are the only supported protocols available for configuration in
  1. To view the routing table:
    tmsh show net route
    You can see what routes the device is dynamically learning from its neighbors. Those routes will have an origin of
  2. To view the current configuration in ZebOS:
    imish -e 'show run'
  3. To remove all running routing protocols in
    tmsh modify net route-domain 0 routing-protocol replace-all-with { }
    You should run this command in case there are multiple routers across multiple-route-domains. If you have multiple route-domains with routers configured, use the command
    zebos check -r <rd num>
    for every route-domain with a router.
    Now you should be able to see that no routing daemons are active if you use the command
    zebos check
  4. Before you recreate the router you had in ZebOS, activate the
    sys db variable
    by typing the command:
    tmsh modify sys db tmrouted.tmos.routing value enable
    Once you have done this, do not enable any routing protocol in the user interface screen
    Route Domains
    , or you will see an error message.
    Once you create a routing instance (BGP or BFD) the system backs upthe routing file in the corresponding route-domain. For example, it is backed up to
    route-domain 0
  5. Now you can recreate the router. For example:
    tmsh create net routing bgp testBGP local-as 111 neighbor add { { remote-as 112} 1::2 { remote-as 112 } } address-family { ipv4 ipv6 { redistribute add { connected kernel static } } }
    It can take about 10 seconds for the daemon to start up.
  6. To view the configuration in ZebOS:
    imish -e 'show run'
    To view the configuration in
    , type:
    tmsh list net routing
  7. To ensure that the routes made their way into ZebOS:
    imish -e 'show ip route'
  8. To verify that you are once again in an established state with the neighbor:
    tmsh show net routing
  9. Once you create the router, the old configuration is backed up automatically. To ensure that the old configuration is backed up, type the command
    cat /zebos/rd<x>/ZebOS.conf.<timestamp>
    where "x" represents the route-domain.
  10. Save your configuration:
    tmsh save sys config
Here is an example of a router and its configuration in
net routing bgp testBGP { address-family { ipv4 { redistribute { kernel { } static { } } } ipv6 { redistribute { connected { } } } } graceful-restart { graceful-reset enabled restart-time 101 stalepath-time 44 } local-as 123 neighbor { 5:6:7::8 { address-family { ipv4 { activate disabled } ipv6 { } } remote-as 114 } { address-family { ipv4 { } ipv6 { activate disabled } } remote-as 113 } } profile bgp route-domain 0 }
Here is the above router's ZebOS equivalent :
! service password-encryption ! bgp extended-asn-cap ! router bgp 123 bgp graceful-restart restart-time 101 bgp graceful-restart stalepath-time 44 bgp graceful-restart graceful-reset redistribute kernel redistribute static neighbor remote-as 113 neighbor 5:6:7::8 remote-as 114 no neighbor 5:6:7::8 activate no neighbor 5:6:7::8 capability graceful-restart ! address-family ipv6 redistribute connected no neighbor activate no neighbor capability graceful-restart neighbor 5:6:7::8 activate exit-address-family ! line con 0 login line vty 0 39 login ! end