Date created: Wednesday, January 12, 2022 1:00:45 PM. Last modified: Thursday, February 24, 2022 11:53:20 AM

Route-Domain Troubleshooting

Running Commands within a Routing Domain

One can see in the following example device config a route-domain with ID 20, and under that RD the load-balancer has an interface configred with ip

net route-domain Common/lab-rd {
    description "LAB Route Domain"
    id 20
    routing-protocol {
    vlans {
net self lab/ {
allow-service {
floating enabled
partition lab
traffic-group Common/traffic-group-1
unit 1
vlan lab/lab-server-vlan2


One can also list routing-domains and their ID on the CLI:

username@(ls100-is)(cfg-sync In Sync)(Active)(/Common)(tmos)# list auth partition
auth partition Common {
    description "Repository for system objects and shared objects."
auth partition lab {
    default-route-domain 20
    description "LAB Route Domain"
auth partition so {
    default-route-domain 30
    description "SO Partition"
auth partition su {
    default-route-domain 10
    description "SU Partition"


If one wants to issue commands on the CLI inside a routing domain one can use the Zebos CLI.

In order to run a traceroute from this RD, one must use Zebos which is initiated using the "imish" command from "tmsh" (the traffic manager shell), and specify the route-domain ID:

username@(ls101-is)(cfg-sync In Sync)(Standby)(/Common)(tmos)# imish -r 20
ls101-is[20]#traceroute ip

^ This traceroute will now come from


Previous page: MST over L2TPv3
Next page: Sys DB