11-25-2011
Hi,
just for sake of completeness: did you experience this issue after an update/installazion of obsolete/new software, just after installation or all of a sudden?
see ya
fra
10 More Discussions You Might Find Interesting
1. Solaris
I have a multipath system with 2 physicals, a virtual and a failsafe. All network connectivity is working fine to and from all of the interfaces and the virtual. The one thing that is not working is 'ping -s'. From this machine, I cannot send and receive packets using ping -s. ping without the... (1 Reply)
Discussion started by: tjlst15
1 Replies
2. HP-UX
Hi.
I just installed the HP-UX 11i V2.
I have problems with CDE - it is inoperative (after logon there is a message box: messaging system failure - or something like that, it asks to check /etc/hosts and network settings).
nslookup works by hostname and IP, hostname shown the correct... (7 Replies)
Discussion started by: netwalker
7 Replies
3. Solaris
Hi All,
My current setup is:
1x Windows Server (Windows 2000 server)
1x Unix Server
2x Windows machine
3x Unix Terminals (Hostnames = A, B and C)
Problem
The problem iam having is Unix terminal C cannot be ping across by Unix terminal A or B or Unix server by using the hostname. Unix... (1 Reply)
Discussion started by: tlee
1 Replies
4. Solaris
I recently installed Solaris 10 on my Sun workstation. I cannot ping using hostname from another computer on the same network.
But I can ping using the IP address. Also I can ping other systems using their hostnames.
Can anyone give some information regarding how to resolve this issue. (4 Replies)
Discussion started by: alpha123
4 Replies
5. AIX
Hello everyone
I have a partition with a problem with ping.
If I do a ping by ip for example ping 1.1.1.1 I got no problem but If I ping by hostname for example ping partition1 take almost a minute to respond me.
I have Aix 5.3 and I have another 19 partitions with no problem. The only... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies
6. UNIX for Dummies Questions & Answers
hi guys
I got something I haven't been able to fix
I configure a Linux Suse 10 box, added static IP, DNS (resolv), gateway (routes) but I am not able to ping other servers by name but nslookup works and the server can navigate on internet
check below
the problematic server is server-host20
... (4 Replies)
Discussion started by: kopper
4 Replies
7. Solaris
hi....
i have sun solaris 10 server, fedora 10, and Windows Server.. i cant ping my sun solaris 10, fedora 10 and Windows Server using hostname (etc: ping winserver.bengkel2.com), but i can ping all using IPV4 and IPV6 address.. can u give some suggestion to solve my problem or some idea to... (3 Replies)
Discussion started by: izuan_7657
3 Replies
8. Shell Programming and Scripting
Hi
We have some 300 servers in the Data center and some of them are running with AIX and some of them are running with Solaris.
I need a script which can be run in one of the server and that script should ping the hostname of all the 300 servers.
Also the script should notify if any server is... (9 Replies)
Discussion started by: newtoaixos
9 Replies
9. Red Hat
Hi Team
we have created a DNS server at RHEL6.2 environment in 10.20.203.x/24 network.
Everything is going well on linux client as nslookup, ping by host etc in entire subnet. We are getting problem in windows client as nslookup working as well but not ping. all the firewall is disabled and... (5 Replies)
Discussion started by: boby.kumar
5 Replies
10. IP Networking
I have vmware on my windows PC ( hostname : acer ).
vmware has RHEL 7 ( hostname : rhel7 ) installed recently.
RHEL IP configuration
IP : 192.168.5.128
Netmask : 255.255.255.0
ssh to rhel7 works from acer using putty
resolve.conf
cat /etc/resolv.conf
nameserver 192.168.5.1
host... (12 Replies)
Discussion started by: hiten.r.chauhan
12 Replies
LEARN ABOUT HPUX
lcpu_attr
lcpu_attr(5) File Formats Manual lcpu_attr(5)
NAME
lcpu_attr - dynamically enable or disable LCPU attribute of the default processor set
VALUES
Fail Safe
Default
the LCPU attribute of the default processor set is disabled
Allowed values
or
DESCRIPTION
This tunable dynamically enables or disables the logical processor (LCPU) attribute in the default processor set. On systems supporting
hyper-threading technology, each hyper-thread is represented as an LCPU.
When the LCPU attribute is enabled, the processor cores in the default processor have hyper-threading enabled. If the LCPU attribute is
disabled, the physical processors in the default processor set behave as single threaded processor cores.
See pset_setattr(2) for information about managing the LCPU attribute in processor sets other than the default processor set.
Who Is Expected to Change This Tunable?
System administrators that wish to change hyper-threading ability in the default processor set.
Restrictions on Changing
The tunable has no effect on platforms that do not have hyper-threading capability or systems with hyper-threading disabled at the firmware
level. On systems that support hyper-threading, the firmware feature must be enabled to dynamically enable/disable the LCPU attribute in
the default processor set.
When Should the Tunable Be Turned On?
The tunable should be turned on to enable the LCPU attribute in the default processor set to take advantage of hyper-threading. If the
applications running on the system see performance benefits, the LCPU attribute should remain enabled.
What Are the Side Effects of Turning the Tunable On?
Some workloads may experience performance degradation when the LCPU attribute is enabled.
When Should the Tunable Be Turned Off?
Some applications may experience performance degradation or may not see any performance benefits from using hyper-threading. In this case,
this tunable should be turned off.
What Are the Side Effects of Turning the Tunable Off?
With LCPU turned off, applications may not take advantage of hyper-threading.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
psrset(1M), pset_assign(2), pset_bind(2), pset_create(2), pset_ctl(2), pset_destroy(2), privgrp(4).
Tunable Kernel Parameters lcpu_attr(5)