configuration. For example, a Red Hat Linux host running only RIPv2 might use the following commands to ensure that routing restarts after a system shutdown: [root]# chkconfig –level 35 zebra on [root]# chkconfig –level 35 ripd on On the other hand, a Red Hat system acting as an external router might use the following: [root]# chkconfig –level 35 zebra on [root]# chkconfig –level 35 ospfd on [root]# chkconfig –level 35 bgpd on If your system does not include startup scripts, the routing manager and the daemons can be started directly, either from the command prompt or from the rc.local script, using the following commands: [root]# zebra -d [root]# ospfd -d [root]# bgpd -d The -d option causes the selected program to run as a daemon. Another commonly used option is -f, which defines the path to the program’s configuration file. Of course, our sample Red Hat system does include startup files in the Zebra RPM to ensure that Zebra starts every time the system reboots. Invoke the startup scripts directly to start the routing manager and the routing daemons immediately. For example: [root]# service zebra start Starting zebra: [ OK ] [root]# service ospfd start Starting ospfd: [ OK ] [root]# service bgpd start Starting bgpd: [ OK ] These commands show the zebra routing manager, the OSPF daemon, and the BGP daemon starting successfully. This happens only after zebra, ospfd, and bgpd are configured because the Red Hat startup scripts check that the configuration files exist before running the programs. Before you start the daemons, create the required configuration files. Zebra Configuration Files Each program in the Zebra suite has its own configuration file. By default, the configuration files are located in the /usr/local/etc directory. On our sample Red Hat system, they are located in the / etc/zebra directory. Each file has a name in the format program.conf, where program is the name of the program being configured. For example, zebra.conf, ospfd.conf, and ripd.conf are all standard configuration filenames. Of course, you can name the configuration file anything you want and place it anywhere on the system because the file can be identified to the program using the -f command-line option when the program is run. However, it is best to stick with standard names, so that others can easily find the files when performing maintenance. Because the routing manager and the various protocols are configured separately, and because modern routing protocols can be very complex, there are hundreds of configuration commands available for Zebra. The “Command Index” section of the HTML documentation that comes with Zebra lists them all. We do not repeat that list here, for a couple of reasons. First, the laundry list of commands is already provided in the online Zebra documentation Zebra provides excellent HTML 208
Note: If you are looking for cheap and reliable provider to host and run your servlet application check Vision servlet hosting services