Manual Chapter :
Move ZebOS BGP and BFD routing
configuration to tmsh
Applies To:
Show Versions
BIG-IP LTM
- 13.1.1, 13.1.0
Move ZebOS BGP and BFD routing
configuration to tmsh
The
same commands used in ZebOS
imish
for BGP and BFD can be used in tmsh
with a few exceptions, as noted
in the HTML files located in the downloads section on support.f5.com. 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
tmsh
.- To view the routing table:tmsh show net routeYou can see what routes the device is dynamically learning from its neighbors. Those routes will have an origin ofdynamic.
- To view the current configuration in ZebOS:imish -e 'show run'
- To remove all running routing protocols intmsh: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 commandzebos 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 commandzebos check.
- Before you recreate the router you had in ZebOS, activate thesys db variableby typing the command:tmsh modify sys db tmrouted.tmos.routing value enableOnce you have done this, do not enable any routing protocol in the user interface screen, 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 tozebos/rd0/ZebOS.conf.<timestamp>forroute-domain 0.
- Now you can recreate the router. For example:tmsh create net routing bgp testBGP local-as 111 neighbor add { 1.1.1.2 { 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.
- To view the configuration in ZebOS:imish -e 'show run'To view the configuration intmsh, type:tmsh list net routing
- To ensure that the routes made their way into ZebOS:imish -e 'show ip route'
- To verify that you are once again in an established state with the neighbor:tmsh show net routing
- Once you create the router, the old configuration is backed up automatically. To ensure that the old configuration is backed up, type the commandcat /zebos/rd<x>/ZebOS.conf.<timestamp>where "x" represents the route-domain.
- Save your configuration:tmsh save sys config
Here is an example of a router and its
configuration in
tmsh
:
Here is the above router's ZebOS equivalent :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 } 1.2.3.4 { address-family { ipv4 { } ipv6 { activate disabled } } remote-as 113 } } profile bgp route-domain 0 }
! 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 1.2.3.4 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 1.2.3.4 activate no neighbor 1.2.3.4 capability graceful-restart neighbor 5:6:7::8 activate exit-address-family ! line con 0 login line vty 0 39 login ! end