Generic Routing FAQs
Users typically have the following questions about how to troubleshoot generic routing issues:
How do I save the config files?
The write command from VTYSH saves only ZebOS.conf. Run the save ns config command from NetScaler CLI to save both ns.conf and ZebOS.conf files.
If I have configured both a static default route and a dynamically learned default route, which is the preferred default route?
The dynamically learned route is the preferred default route. This behavior is unique to default routes. However, in case of the Network Services Module (NSM), unless the administrative distances are modified, a statically configured route in the RIB is preferred over a dynamic route. The route that is downloaded to the NSM FIB is the static route.
How do I block the advertisement of default routes?
The default route is not injected into ZebOS.
How do I view the debug output of networking daemons?
You can write debugging output from networking daemons to a file by entering the following log file command from the global configuration view in VTYSH:
ns(config)# log file /var/ZebOS.log
You can direct debug output to the console by entering the terminal monitor command from VTYSH user view:
ns# terminal monitor
How do I collect cores of running daemons?
You can use the gcore utility to collect cores of running daemons for processing by gdb. This might be helpful in debugging misbehaving daemons without bringing the whole routing operation to a standstill.
gcore [-s] [-c core] [executable] pid
The -s option temporarily stops the daemon while gathering the core image. This is a recommended option, because it guarantees that the resulting image shows the core in a consistent state.
root@ns#gcore -s -c nsm.core /netscaler/nsm 342
How do I run a batch of ZebOS commands?
You can run a batch of ZebOS commands from a file by entering the VTYSH -f <file-name> command. This does not replace the running configuration, but appends to it. However, by including commands to delete the existing configuration in the batch file and then add those for the new, desired configuration, you can use this mechanism to replace a specific configuration:
! router bgp 234 network 188.8.131.52 255.255.255.0 ! route-map bgp-out2 permit 10 set metric 9900 set community 8602:300 !