Sponsored Content
Full Discussion: AIX Routing Issue
Operating Systems AIX AIX Routing Issue Post 302134195 by Neo on Wednesday 29th of August 2007 02:34:10 PM
Old 08-29-2007
You need to find any routing daemons that are processing and terminate them, and then insure they don't restart when the system boots.
 

10 More Discussions You Might Find Interesting

1. AIX

AIX 4.3.3.0 routing problems

Hello guys. I have a AIX running an ip of 128.2.1.85 255.255.255.0, Main office router is 128.2.1.2 .we just got an t1 line point to point for a remote office with to pcs. My question. I'm not able to ping those pcs one of them is using this ip 128.2.2.128 255.255.255.0 Remote router ip... (2 Replies)
Discussion started by: josramon
2 Replies

2. UNIX for Dummies Questions & Answers

AIX 5.3 Routing

Hey all you *Nix Gurus...I got a relatively simple one for ya. I just cloned an AIX 5.3 server without copy over the Network info. However, now I need to update the routing table on the destination server so that it mirrors the source. Aside from painstakingly, manually updating the ODM using... (1 Reply)
Discussion started by: BlitzSonik
1 Replies

3. AIX

scripting routing changes on aix 4.3 and 5x

Hi All, I need to script a routing changes on my aix servers. I can't use smitty, very slow. I need to delete the static routing and add a new one. I also need to change default routing. I know using route add and route delete but I think I remember that this is not enough that's why I... (2 Replies)
Discussion started by: itik
2 Replies

4. AIX

Routing setup - AIX

Hi All, I know there is a way to do this in routers. The question is whether it is posisble to do this in AIX. For our Web Focus ODBC connection to the Disaster Recovery servers, we want to restrict the access to the ODBC ports so that only the IP address of the Web Focus server can get to... (1 Reply)
Discussion started by: strunz
1 Replies

5. IP Networking

IP - Routing issue?

I have an IP routing issue or I am just to stupid to work it out myself. I have setup am old PC running SUSE Linux 11.3 as a router, the system has 3 Interfaces connecting 3 networks. Interface 1 = 10.164.2.161/21 Interface 2 = 192.168.1.210/24 Interface 3 = 30.1.0.11/16 The default... (6 Replies)
Discussion started by: hogola
6 Replies

6. IP Networking

Need help with a routing issue.

I have run into a wall troubleshooting a Centos 5 networking issue. Hoping someone can assist. I've got a box with two vlans trunked over bond0 bond0 Link encap:Ethernet HWaddr 00:22:64:C1:D6:60 inet6 addr: fe80::222:64ff:fec1:d660/64 Scope:Link ... (0 Replies)
Discussion started by: creedog
0 Replies

7. AIX

Aix Routing Problem

I need the following solution , please help me... Current situation ip: 192.168.0.12 persistent and 192.168.254.12 service ip gateway: 192.168.0.254 subnet: 255.255.255.0 i have added a new ip on a new nic ip: 10.10.255.40 gateway: 10.10.255.62 subnet: 255.255.255.224 ... (1 Reply)
Discussion started by: rajibimran
1 Replies

8. UNIX for Dummies Questions & Answers

Routing issue - local vs LAN

hi guys suse 11 SP1 x64 I have a server (4 NIC ports 192.168.100.100-103) that connects point to point to a storage device (same thing 4 ports 192.168.110.100-113) but this server connects to normal LAN 10.6.100.x - gateway 10.6.100.1 the issue is when testing connectivity to the storage... (7 Replies)
Discussion started by: karlochacon
7 Replies

9. IP Networking

This looks like a tough routing issue

Hi, The default gateway (172.17.220.1) cannot be pinged via the default interface bond0 (172.17.220.231), but can be pinged via interface eth1 (10.201.135.73). # ping -I eth1 172.17.220.1 PING 172.17.220.1 (172.17.220.1) from 10.201.135.73 eth1: 56(84) bytes of data. 64 bytes from... (4 Replies)
Discussion started by: aixlover
4 Replies

10. Solaris

Routing Issue

we are not able to ping client server (falcon-ebr.sbms.bsc.com) from netbackup master server (135.179.96.122 tsprd-ebr.edc.single.net) However from client server we are able to ping the master Server. Please assist on this (1 Reply)
Discussion started by: Rahul466
1 Replies
WATCHQUAGGA(8)						      System Manager's Manual						    WATCHQUAGGA(8)

NAME
watchquagga - a program to monitor the status of quagga daemons SYNOPSIS
watchquagga [option...] daemon... watchquagga -h | -v DESCRIPTION
watchquagga is a watchdog program that monitors the status of supplied quagga daemons and tries to restart them in case they become unre- sponsive or shut down. To determine whether a daemon is running, it tries to connect to the daemon's VTY UNIX stream socket, and send echo commands to ensure the daemon responds. When the daemon crashes, EOF is received from the socket, so that watchquagga can react immediately. This program can run in one of the following 5 modes: Mode 0: monitor In this mode, the program serves as a monitor and reports status changes. Example usage: watchquagga -d zebra ospfd bgpd Mode 1: global restart In this mode, whenever a daemon hangs or crashes, the given command is used to restart all watched daemons. Example usage: watchquagga -dz -R '/sbin/service zebra restart; /sbin/service ospfd restart' zebra ospfd Mode 2: individual daemon restart In this mode, whenever a single daemon hangs or crashes, the given command is used to restart this daemon only. Example usage: watchquagga -dz -r '/sbin/service %s restart' zebra ospfd bgpd Mode 3: phased zebra restart In this mode, whenever a single daemon hangs or crashes, the given command is used to restart this daemon only. The only exception is the zebra daemon; in this case, the following steps are taken: (1) all other daemons are stopped, (2) zebra is restarted, and (3) other daemons are started again. Example usage: watchquagga -adz -r '/sbin/service %s restart' -s '/sbin/service %s start' -k '/sbin/service %s stop' zebra ospfd bgpd Mode 4: phased global restart for any failure In this mode, whenever a single daemon hangs or crashes, the following steps are taken: (1) all other daemons are stopped, (2) zebra is restarted, and (3) other daemons are started again. Example usage: watchquagga -Adz -r '/sbin/service %s restart' -s '/sbin/service %s start' -k '/sbin/service %s stop' zebra ospfd bgpd Important: It is believed that mode 2 (individual daemon restart) is not safe, and mode 3 (phased zebra restart) may not be safe with cer- tain routing daemons. In order to avoid restarting the daemons in quick succession, you can supply the -m and -M options to set the minimum and maximum delay between the restart commands. The minimum restart delay is recalculated each time a restart is attempted. If the time since the last restart attempt exceeds twice the value of -M, the restart delay is set to the value of -m, otherwise the interval is doubled (but capped at the value of -M). OPTIONS
-d, --daemon Run in daemon mode. When supplied, error messages are sent to Syslog instead of standard output (stdout). -S directory, --statedir directory Set the VTY socket directory (the default value is "/var/run/quagga"). -e, --no-echo Do not ping the daemons to test whether they respond. This option is necessary if one or more daemons do not support the echo com- mand. -l level, --loglevel level Set the logging level (the default value is "6"). The value should range from 0 (LOG_EMERG) to 7 (LOG_DEBUG), but higher number can be supplied if extra debugging messages are required. -m number, --min-restart-interval number Set the minimum number of seconds to wait between invocations of the daemon restart commands (the default value is "60"). -M number, --max-restart-interval number Set the maximum number of seconds to wait between invocations of the daemon restart commands (the default value is "600"). -i number, --interval number Set the status polling interval in seconds (the default value is "5"). -t number, --timeout number Set the unresponsiveness timeout in seconds (the default value is "10"). -T number, --restart-timeout number Set the restart (kill) timeout in seconds (the default value is "20"). If any background jobs are still running after this period has elapsed, they will be killed. -r command, --restart command Supply a Bourne shell command to restart a single daemon. The command string should contain the '%s' placeholder to be substituted with the daemon name. Note that -r and -R options are not compatible. -s command, --start-command command Supply a Bourne shell command to start a single daemon. The command string should contain the '%s' placeholder to be substituted with the daemon name. -k command, --kill-command command Supply a Bourne shell command to stop a single daemon. The command string should contain the '%s' placeholder to be substituted with the daemon name. -R, --restart-all When one or more daemons are shut down, try to restart them using the Bourne shell command supplied on the command line. Note that -r and -R options are not compatible. -z, --unresponsive-restart When a daemon is in an unresponsive state, treat it as being shut down for the restart purposes. -a, --all-restart When zebra hangs or crashes, restart all daemons taking the following steps: (1) stop all other daemons, (2) restart zebra, and (3) start other daemons again. Note that this option also requires -r, -s, and -k options to be specified. -A, --always-all-restart When any daemon (i.e., not just zebra) hangs or crashes, restart all daemons taking the following steps: (1) stop all other daemons, (2) restart zebra, and (3) start other daemons again. Note that this option also requires -r, -s, and -k options to be specified. -p filename, --pid-file filename Set the process identifier filename (the default value is "/var/run/quagga/watchquagga.pid"). -b string, --blank-string string When the supplied string is found in any of the command line option arguments (i.e., -r, -s, -k, or -R), replace it with a space. This is an ugly hack to circumvent problems with passing the command line arguments containing embedded spaces. -v, --version Display the version information and exit. -h, --help Display the usage information and exit. SEE ALSO
zebra(8), bgpd(8), isisd(8), ospfd(8), ospf6d(8), ripd(8), ripngd(8) See the project homepage at <http://www.quagga.net/>. AUTHORS
Copyright 2004 Andrew J. Schorr July 2010 WATCHQUAGGA(8)
All times are GMT -4. The time now is 06:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy