Sponsored Content
Full Discussion: Cluster failure reason
Operating Systems AIX Cluster failure reason Post 302885229 by Tharsan on Friday 24th of January 2014 09:41:53 AM
Old 01-24-2014
Thank you,

I can i check the gatway because the ping and traceroute command don't specify the gateway

---------- Post updated at 03:41 PM ---------- Previous update was at 03:18 PM ----------

Do you know how its working the IBM "active dead gateway detection" ?
The format of the standard output ?
 

8 More Discussions You Might Find Interesting

1. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

2. High Performance Computing

SUN Cluster Vs Veritas Cluster

Dear All, Can anyone explain about Pros and Cons of SUN and Veritas Cluster ? Any comparison chart is highly appreciated. Regards, RAA (4 Replies)
Discussion started by: RAA
4 Replies

3. Solaris

Subject: Sun Cluster 3.2.2 Apache HA failure, or cludge?

I folks, season's greetings. Hope you had a good festive season. I've got 2 related problems on the same Sun Cluster 3.2.2 Apache 2.0.63 cluster: clsetup error: ERROR: Failed to get connection to node localhost SunOS... (0 Replies)
Discussion started by: cluster
0 Replies

4. Solaris

Sun cluster and Veritas cluster question.

Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC. Am thinking how to migrate to sun cluster setup instead. My plan as follows leave the existing vcs intact as a fallback plan. Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies

5. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

6. Solaris

Sun cluster 4.0 - zone cluster failover doubt

Hello experts - I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts. (1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over) (2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies

7. Red Hat

Problem in RedHat Cluster Node while network Failure or in Hang mode

Hi, We are having many RedHat linux Server with Cluster facility for availability of service like HTTPD / MySQL. We face some issue while some issue related to power disturbance / fluctuation or Network failure. There is two Cluster Node configured in... (0 Replies)
Discussion started by: hirenkmistry
0 Replies

8. Shell Programming and Scripting

How to get reason for ping failure using perls Net::Ping->new("icmp");?

Hi I am using perl to ping a list of nodes - with script below : $p = Net::Ping->new("icmp"); if ($p->ping($host,1)){ print "$host is alive.\n"; } else { print "$host is unreacheable.\n"; } $p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies
TRACEROUTE6(8)						    BSD System Manager's Manual 					    TRACEROUTE6(8)

NAME
traceroute6 -- print the route IPv6 packets will take to a network node SYNOPSIS
traceroute6 [-dIlnNrvU] [-f firsthop] [-g gateway] [-m hoplimit] [-p port] [-q probes] [-s src] [-w waittime] target [datalen] DESCRIPTION
The traceroute6 utility uses the IPv6 protocol hop limit field to elicit an ICMPv6 TIME_EXCEEDED response from each gateway along the path to some host. The only mandatory parameter is the destination host name or IPv6 address. The default probe datagram carries 12 bytes of payload, in addi- tion to the IPv6 header. The size of the payload can be specified by giving a length (in bytes) after the destination host name. Other options are: -d Debug mode. -f firsthop Specify how many hops to skip in trace. -g gateway Specify intermediate gateway (traceroute6 uses routing header). -I Use ICMP6 ECHO instead of UDP datagrams. -l Print both host hostnames and numeric addresses. Normally traceroute6 prints only hostnames if -n is not specified, and only numeric addresses if -n is specified. -m hoplimit Specify maximum hoplimit, up to 255. The default is 30 hops. -n Do not resolve numeric address to hostname. -N Use a packet with no upper layer header for the probes, instead of UDP datagrams. -p port Set UDP port number to port. -q probes Set the number of probe per hop count to probes. -r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly-connected net- work, an error is returned. This option corresponds to the SO_DONTROUTE socket option; it can be used to ping a local host through an interface that has no route through it (e.g., after the interface was dropped by a routing daemon). -s src Src specifies the source IPv6 address to be used. -U Use UDP datagrams for the probes. This is the default. -v Be verbose. -w waittime Specify the delay time between probes. This program prints the route to the given destination and the round-trip time to each gateway, in the same manner as traceroute. Here is a list of possible annotations after the round-trip time for each gateway: !N Destination Unreachable - No Route to Host. !P Destination Unreachable - Administratively Prohibited. !S Destination Unreachable - Not a Neighbour. !A Destination Unreachable - Address Unreachable. ! This is printed if the hop limit is <= 1 on a port unreachable message. This means that the packet got to the destination, but that the reply had a hop limit that was just large enough to allow it to get back to the source of the traceroute6. This was more interesting in the IPv4 case, where some IP stack bugs could be identified by this behaviour. RETURN VALUES
The traceroute6 utility will exit with 0 on success, and non-zero on errors. SEE ALSO
ping(8), ping6(8), traceroute(8) HISTORY
The traceroute6 utility first appeared in WIDE hydrangea IPv6 protocol stack kit. BSD
May 17, 1998 BSD
All times are GMT -4. The time now is 10:20 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy