Date created: 01/12/22 13:00:45. Last modified: 02/24/22 11:53:20

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 10.244.148.1:

net route-domain Common/lab-rd {
    description "LAB Route Domain"
    id 20
    routing-protocol {
        BFD
        BGP
    }
    vlans {
        lab/lab-server-vlan3
        lab/lab-server-vlan1
        lab/lab-server-vlan2
        lab/lab-slb-fw
    }
}
...
net self lab/10.244.148.1/23 {
address 10.244.148.1%20/23
allow-service {
icmp:any
}
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]>enable
ls101-is[20]#traceroute ip 10.10.10.10

^ This traceroute will now come from 10.244.148.1

 


Previous page: MST over L2TPv3
Next page: Sys DB