Sponsored Content
Operating Systems AIX AIX server problem - network connection is unstable ! Post 303045164 by zxmaus on Thursday 12th of March 2020 11:35:50 PM
Old 03-13-2020
we have P8 850s, 870s and P9 950s with various amounts of memory between about 256 GB up to 4 TB memory and anywhere between 40 and 128 cpus. Not virtualized. A lot less adapters (usually 4 HBAs and 4 NICs - with Oracle 12c and 19 (thats at least what the DBAs tell us). We do not have GPFS but that should not make any difference for network realistically, only for IO. OS level for us is 7.2.3.3, and we have 2-node clusters.
These 2 Users Gave Thanks to zxmaus For This Post:
 

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
NUMACTL(8)						   Linux Administrator's Manual 						NUMACTL(8)

NAME
numactl - Control NUMA policy for processes or shared memory SYNOPSIS
numactl [ --interleave nodes ] [ --preferred node ] [ --membind nodes ] [ --cpunodebind nodes ] [ --physcpubind cpus ] [ --localalloc ] [--] command {arguments ...} numactl --show numactl --hardware numactl [ --huge ] [ --offset offset ] [ --shmmode shmmode ] [ --length length ] [ --strict ] [ --shmid id ] --shm shmkeyfile | --file tmpfsfile [ --touch ] [ --dump ] [ --dump-nodes ] memory policy DESCRIPTION
numactl runs processes with a specific NUMA scheduling or memory placement policy. The policy is set for command and inherited by all of its children. In addition it can set persistent policy for shared memory segments or files. Use -- before command if using command options that could be confused with numactl options. nodes may be specified as N,N,N or N-N or N,N-N or N-N,N-N and so forth. Relative nodes may be specifed as +N,N,N or +N-N or +N,N-N and so forth. The + indicates that the node numbers are relative to the process' set of allowed nodes in its current cpuset. A !N-N notation indicates the inverse of N-N, in other words all nodes except N-N. If used with + notation, specify !+N-N. When same is specified the pre- vious nodemask specified on the command line is used. all means all nodes in the current cpuset. Instead of a number a node can also be: netdev:DEV The node connected to network device DEV. file:PATH The node the block device of PATH. ip:HOST The node of the network device of HOST block:PATH The node of block device PATH pci:[seg:]bus:dev[:func] The node of a PCI device. Note that block resolves the kernel block device names only for udev names in /dev use file: Policy settings are: --interleave=nodes, -i nodes Set a memory interleave policy. Memory will be allocated using round robin on nodes. When memory cannot be allocated on the current interleave target fall back to other nodes. Multiple nodes may be specified on --interleave, --membind and --cpunodebind. --membind=nodes, -m nodes Only allocate memory from nodes. Allocation will fail when there is not enough memory available on these nodes. nodes may be spec- ified as noted above. --cpunodebind=nodes, -N nodes Only execute command on the CPUs of nodes. Note that nodes may consist of multiple CPUs. nodes may be specified as noted above. --physcpubind=cpus, -C cpus Only execute process on cpus. This accepts cpu numbers as shown in the processor fields of /proc/cpuinfo, or relative cpus as in relative to the current cpuset. You may specify "all", which means all cpus in the current cpuset. Physical cpus may be specified as N,N,N or N-N or N,N-N or N-N,N-N and so forth. Relative cpus may be specifed as +N,N,N or +N-N or +N,N-N and so forth. The + indicates that the cpu numbers are relative to the process' set of allowed cpus in its current cpuset. A !N-N notation indicates the inverse of N-N, in other words all cpus except N-N. If used with + notation, specify !+N-N. --localalloc, -l Always allocate on the current node. --preferred=node Preferably allocate memory on node, but if memory cannot be allocated there fall back to other nodes. This option takes only a sin- gle node number. Relative notation may be used. --show, -s Show NUMA policy settings of the current process. --hardware, -H Show inventory of available nodes on the system. Numactl can set up policy for a SYSV shared memory segment or a file in shmfs/hugetlbfs. This policy is persistent and will be used by all mappings from that shared memory. The order of options matters here. The specification must at least include either of --shm, --shmid, --file to specify the shared memory segment or file and a memory policy like described above ( --interleave, --localalloc, --preferred, --membind ). --huge When creating a SYSV shared memory segment use huge pages. Only valid before --shmid or --shm --offset Specify offset into the shared memory segment. Default 0. Valid units are m (for MB), g (for GB), k (for KB), otherwise it specifies bytes. --strict Give an error when a page in the policied area in the shared memory segment already was faulted in with a conflicting policy. Default is to silently ignore this. --shmmode shmmode Only valid before --shmid or --shm When creating a shared memory segment set it to numeric mode shmmode. --length length Apply policy to length range in the shared memory segment or make the segment length long Default is to use the remaining length Required when a shared memory segment is created and specifies the length of the new segment then. Valid units are m (for MB), g (for GB), k (for KB), otherwise it specifies bytes. --shmid id Create or use an shared memory segment with numeric ID id --shm shmkeyfile Create or use an shared memory segment, with the ID generated using ftok(3) from shmkeyfile --file tmpfsfile Set policy for a file in tmpfs or hugetlbfs --touch Touch pages to enforce policy early. Default is to not touch them, the policy is applied when an applications maps and accesses a page. --dump Dump policy in the specified range. --dump-nodes Dump all nodes of the specific range (very verbose!) Valid node specifiers all All nodes number Node number number1{,number2} Node number1 and Node number2 number1-number2 Nodes from number1 to number2 ! nodes Invert selection of the following specification. EXAMPLES
numactl --physcpubind=+0-4,8-12 myapplic arguments Run myapplic on cpus 0-4 and 8-12 of the current cpuset. numactl --interleave=all bigdatabase arguments Run big database with its memory interleaved on all CPUs. numactl --cpunodebind=0 --membind=0,1 process Run process on node 0 with memory allocated on node 0 and 1. numactl --cpunodebind=0 --membind=0,1 -- process -l Run process as above, but with an option (-l) that would be confused with a numactl option. numactl --nodebind=netdev:eth0 --membind=netdev:eth0 network-server Run network-server on the node of network device eth0 with its memory also in the same node. numactl --preferred=1 numactl --show Set preferred node 1 and show the resulting state. numactl --interleave=all --shmkeyfile /tmp/shmkey Interleave all of the sysv shared memory region specified by /tmp/shmkey over all nodes. Place a tmpfs file on 2 nodes: numactl --membind=2 dd if=/dev/zero of=/dev/shm/A bs=1M count=1024 numactl --membind=3 dd if=/dev/zero of=/dev/shm/A seek=1024 bs=1M count=1024 numactl --localalloc /dev/shm/file Reset the policy for the shared memory file file to the default localalloc policy. NOTES
Requires an NUMA policy aware kernel. Command is not executed using a shell. If you want to use shell metacharacters in the child use sh -c as wrapper. Setting policy for a hugetlbfs file does currently not work because it cannot be extended by truncate. Shared memory segments larger than numactl's address space cannot be completely policied. This could be a problem on 32bit architectures. Changing it piece by piece may work. The old --cpubind which accepts node numbers, not cpu numbers, is deprecated and replaced with the new --cpunodebind and --physcpubind options. FILES
/proc/cpuinfo for the listing of active CPUs. See proc(5) for details. /sys/devices/system/node/node*/numastat for NUMA memory hit statistics. COPYRIGHT
Copyright 2002,2004 Andi Kleen, SuSE Labs. numactl and the demo programs are under the GNU General Public License, v.2 SEE ALSO
set_mempolicy(2) , get_mempolicy(2) , mbind(2) , sched_setaffinity(2) , sched_getaffinity(2) , proc(5) , ftok(3) , shmat(2) , migratepages(8) SuSE Labs Mar 2004 NUMACTL(8)

Featured Tech Videos

All times are GMT -4. The time now is 10:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy