Sponsored Content
Operating Systems AIX AIX server problem - network connection is unstable ! Post 303044592 by bobochacha29 on Thursday 27th of February 2020 05:00:58 AM
Old 02-27-2020
AIX server problem - network connection is unstable !

Our company has just bought 2 IBM servers P8 - to make a Database Cluster. We've finished the installation progresses, but now there's a problem: the network connection is unstable - like this

Code:
sysopr1@ic_tsm:/home/sysopr1>ping 10.0.91.18
PING 10.0.91.18: (10.0.91.18): 56 data bytes
64 bytes from 10.0.91.18: icmp_seq=0 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=1 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=2 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=3 ttl=255 time=42 ms
64 bytes from 10.0.91.18: icmp_seq=4 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=5 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=6 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=7 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=8 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=9 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=10 ttl=255 time=48 ms
64 bytes from 10.0.91.18: icmp_seq=11 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=12 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=13 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=14 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=15 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=16 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=17 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=18 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=19 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=20 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=21 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=22 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=23 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=24 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=25 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=26 ttl=255 time=3 ms
64 bytes from 10.0.91.18: icmp_seq=27 ttl=255 time=0 ms
64 bytes from 10.0.91.18: icmp_seq=28 ttl=255 time=44 ms

We ping these two new servers from many servers with diffirences vlan, but it's always like that. This's really a big problem because the Oracle RAC requies the "time"" parametter must be <3.

Could someone help please ! Thanks

Moderator's Comments:
Mod Comment Code tags please, not Quotes, thanks

Last edited by vbe; 02-27-2020 at 06:24 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

FTP connection problem on new server

Solaris Server (V880) version 8 Brand new box just installed O/S, what do I need to do in order to get FTP working. I have updated the /etc/hosts.equiv file Problem - When trying to ftp to the server I get a login incorrect message, this is with the root user. Are there some... (1 Reply)
Discussion started by: miredale
1 Replies

2. UNIX for Dummies Questions & Answers

Network connection problem in unix

I have a network connection problem in unix. I am trying to access to LAN in unix but unfortunately it doesn't work. For example, if I ping from Unix to windows it says 'the network is unreacable'. Also, I can't ping in windows to unix. I would be glad if someone could help me. Thanks. ... (5 Replies)
Discussion started by: fatihshen
5 Replies

3. Cybersecurity

Enable SSH for root over certain network connection of a server...is it possible?

Hi - I have a SUSE Enterprise Linux Server V9 that I have an issue with. Policy says that root connectivity via ssh needs to be disabled. So, to do that, I made the following change in the sshd_config section: # Authentication: #LoginGraceTime 2m #PermitRootLogin yes PermitRootLogin no... (3 Replies)
Discussion started by: cpolikowsky
3 Replies

4. Solaris

Server unexpectedly closed network connection error in passwordless in ssh through

Hi , when i try to passwordless connection login in ssh through putty, i am getting the "Server unexpectedly closed network connection" error.i have already finished the public and private key settings for the particular user. thanks MaroV (1 Reply)
Discussion started by: vr_mari
1 Replies

5. AIX

AIX OS problem? network problem?

Dear ALL. I installed AIX OS on customer sites. but Only one site is too slow when I connected telnet, ftp.. Ping is too fast. but telnet and FTP is not connected.. of course i check the configuration file on aix but it's normal. Do any Idea?? thanks in advance. - Jun - (3 Replies)
Discussion started by: Jeon Jun Seok
3 Replies

6. Solaris

Solaris 10 ftp connection problem (connection refused, connection timed out)

Hi everyone, I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies

7. AIX

Help Me - AIX server connect to a VPN network

Hi, I have a task requested by my boss to create a script to enable a server to connect to a vpn network and then to connect to another server to upload some data... How can I connect to a vpn network from AIX server? via telnet? ssh? I have tried to google but mostly the answers are... (1 Reply)
Discussion started by: mushr00m
1 Replies

8. UNIX for Advanced & Expert Users

fork: Resource temporarily unavailable , server unexpectedly unavailable network connection

Solaris 10 Server refuse to connect :wall: fork: Resource temporarily unavailable , server unexpectedly unavailable network connection , refuse error, disconnect message, fatal error type2, (protocol error type2) Issue has been resolved after taken few steps :b: First of all need to check... (1 Reply)
Discussion started by: taherahmed
1 Replies

9. Ubuntu

ssh connection unstable on remote server

Hi I hope someone can spot what is wrong with this ssh connection as it has me baffled. I am trying to set up a remote ssh connection (passwordless) to a remote 'server', (Ubuntu laptop at home). I have tried these steps with rsa and dsa key types, (currently dsa) - 1) ssh-keygen... (4 Replies)
Discussion started by: steadyonabix
4 Replies

10. AIX

FTP connection refused from text editor while accessing AIX server .

HI , I'm facing the FTP connection refused from text editor while accessing AIX server .It showing the messege "can't create ftp connection connectin refused".Though it is accessible from putty . i'm using aix version 6 . Can any one let me know the seetings needs to be made so that i... (2 Replies)
Discussion started by: rmkganesh
2 Replies
ping(1M)						  System Administration Commands						  ping(1M)

NAME
ping - send ICMP (ICMP6) ECHO_REQUEST packets to network hosts SYNOPSIS
/usr/sbin/ping host [timeout] /usr/sbin/ping -s [-l | -U] [-adlLnrRv] [-A addr_family] [-c traffic_class] [-g gateway [ -g gateway...]] [-F flow_label] [-I interval] [-i interface] [-P tos] [-p port] [-t ttl] host [data_size] [npackets] DESCRIPTION
The utility ping utilizes the ICMP (ICMP6 in IPv6) protocol's ECHO_REQUEST datagram to elicit an ICMP (ICMP6) ECHO_RESPONSE from the speci- fied host or network gateway. If host responds, ping will print: host is alive on the standard output and exit. Otherwise, after timeout seconds, it will write: no answer from host The default value of timeout is 20 seconds. When you specify the s flag, sends one datagram per second (adjust with -I) and prints one line of output for every ECHO_RESPONSE that it receives. ping produces no output if there is no response. In this second form, ping computes round trip times and packet loss statistics; it displays a summary of this information upon termination or timeout. The default data_size is 56 bytes, or you can specify a size with the data_size command-line argument. If you specify the optional npackets, ping sends ping requests until it either sends npackets requests or receives npackets replies. When using ping for fault isolation, first ping the local host to verify that the local network interface is running. OPTIONS
The following options are supported: -A addr_family Specify the address family of the target host. addr_family can be either inet or inet6. Address family determines which protocol to use. For an argument of inet, IPv4 is used. For inet6, IPv6 is used. By default, if the name of a host is provided, not the literal IP address, and a valid IPv6 address exists in the name service database, ping will use this address. Otherwise, if the name service database contains an IPv4 address, it will try the IPv4 address. Specify the address family inet or inet6 to override the default behavior. If the argument specified is inet, ping will use the IPv4 address associated with the host name. If none exists, ping will state that the host is unknown and exit. It does not try to determine if an IPv6 address exists in the name service database. If the specified argument is inet6, ping uses the IPv6 address that is associated with the host name. If none exists, ping states that the host is unknown and exits. -F flow_label Specify the flow label of probe packets. The value must be an integer in the range from 0 to 1048575. This option is valid only on IPv6. -I interval Turn on the statistics mode and specify the interval between successive transmissions. The default is one second. See the discussion of the -s option. -L Turn off loopback of multicast packets. Normally, members are in the host group on the outgoing interface, a copy of the multicast packets will be delivered to the local machine. -P tos Set the type of service (tos) in probe packets to the specified value. The default is zero. The value must be an integer in the range from 0 to 255. Gateways also in the path can route the probe packet differently, depending upon the value of tos that is set in the probe packet. This option is valid only on IPv4. -R Record route. Sets the IPv4 record route option, which stores the route of the packet inside the IPv4 header. The contents of the record route are only printed if the -v and -s options are given. They are only set on return pack- ets if the target host preserves the record route option across echos, or the -l option is given. This option is valid only on IPv4. -U Send UDP packets instead of ICMP (ICMP6) packets. ping sends UDP packets to consecutive ports expecting to receive back ICMP (ICMP6) PORT_UNREACHABLE from the target host. -a ping all addresses, both IPv4 and IPv6, of the multihomed destination. The output appears as if ping has been run once for each IP address of the destination. If this option is used together with -A, ping probes only the addresses that are of the specified address family. When used with the -s option and npackets is not specified, ping continuously probes the destination addresses in a round robin fashion. If npackets is specified, ping sends npackets number of probes to each IP address of the destination and then exits. -c traffic_class Specify the traffic class of probe packets. The value must be an integer in the range from 0 to 255. Gateways along the path can route the probe packet differently, depending upon the value of traffic_class set in the probe packet. This option is valid only on IPv6. -d Set the SO_DEBUG socket option. -g gateway Specify a loose source route gateway so that the probe packet goes through the specified host along the path to the target host. The maximum number of gateways is 8 for IPv4 and 127 for IPv6. Note that some factors such as the link MTU can further limit the number of gateways for IPv6. -i interface_address Specify the outgoing interface address to use for multicast packets for IPv4 and both multicast and unicast packets for IPv6. The default interface address for multicast packets is determined from the (unicast) routing tables. interface_address can be a literal IP address, for example, 10.123.100.99, or an interface name, for example, eri0, or an interface index, for example 2. -l Use to send the probe packet to the given host and back again using loose source routing. Usually specified with the -R option. If any gateways are specified using -g, they are visited twice, both to and from the destination. This option is ignored if the -U option is used. -n Show network addresses as numbers. ping normally does a reverse name lookup on the IP addresses it extracts from the packets received. The -n option blocks the reverse lookup, so ping prints IP addresses instead of host names. -p port Set the base UDP port number used in probes. This option is used with the -U option. The default base port number is 33434. The ping utility starts setting the destination port number of UDP packets to this base and increments it by one at each probe. -r Bypass the normal routing tables and send directly to a host on an attached network. If the host is not on a directly attached network, an error is returned. This option can be used to ping a local host through an interface that has been dropped by the router daemon. See in.routed(1M). -s Send one datagram per second and collect statistics. -t ttl Specify the IPv4 time to live, or IPv6 hop limit, for unicast and multicast packets. The default time to live (hop limit) for unicast packets can be set with the ndd module, /dev/icmp, using the icmp_ipv4_ttl variable for IPv4 and the icmp_ipv6_hoplimit variable for IPv6. The default time to live (hop limit) for multicast is one hop. See EXAM- PLES. For further information, seendd(1M). -v Verbose output. List any ICMP (ICMP6) packets, other than replies from the target host. OPERANDS
host The network host EXAMPLES
Example 1: Using ping With IPv6 This example shows ping sending probe packets to all the IPv6 addresses of the host xyz, one at a time. It sends an ICMP6 ECHO_REQUEST every second until the user interrupts it. istanbul% ping -s -A inet6 -a xyz PING xyz: 56 data bytes 64 bytes from xyz (4::114:a00:20ff:ab3d:83ed): icmp_seq=0. time=0.479 ms 64 bytes from xyz (fec0::114:a00:20ff:ab3d:83ed): icmp_seq=1. time=0.843 ms 64 bytes from xyz (4::114:a00:20ff:ab3d:83ed): icmp_seq=2. time=0.516 ms 64 bytes from xyz (fec0::114:a00:20ff:ab3d:83ed): icmp_seq=3. time=4.94 ms 64 bytes from xyz (4::114:a00:20ff:ab3d:83ed): icmp_seq=4. time=0.485 ms 64 bytes from xyz (fec0::114:a00:20ff:ab3d:83ed): icmp_seq=5. time=2.20 ms ^C ----xyz PING Statistics---- 6 packets transmitted, 6 packets received, 0% packet loss round-trip (ms) min/avg/stddev = 0.479/1.58/4.94/1.8 Example 2: Using ndd to Set the icmp_ipv6_hoplimit This example shows the ndd module, /dev/icmp, used to set the icmp_ipv6_hoplimit. # ndd -set /dev/icmp icmp_ipv6_hoplimit 100 EXIT STATUS
The following exit values are returned: 0 Successful operation; the machine is alive. non-zero An error has occurred. Either a malformed argument has been specified, or the machine was not alive. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWbip | +-----------------------------+-----------------------------+ SEE ALSO
ifconfig(1M), in.routed(1M), ndd(1M), netstat(1M), rpcinfo(1M), traceroute(1M), attributes(5), icmp(7P), icmp6(7P) SunOS 5.10 11 Mar 2004 ping(1M)
All times are GMT -4. The time now is 08:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy