Thursday, March 12, 2015

Prevent Syslog from accepting messages from the network HPUX

$ grep SYSLOGD /etc/rc.config.d/syslogd
# SYSLOGD_OPTS: Options to be used when starting up syslogd.
SYSLOGD_OPTS="-N -D -v"
$





The option -N will disable syslogd to accept logs from network.

Wednesday, February 11, 2015

Start NFS hpux 11.31

# /sbin/init.d/nfs.core start
    Starting NFS CORE networking

    Starting up the rpcbind
        /usr/sbin/rpcbind
# /sbin/init.d/nfs.client start
    Starting NFS CLIENT subsystem

ERROR: rpc.statd not running.  Run "/sbin/init.d/lockmgr start" to start rpc.statd, exiting
# /sbin/init.d/lockmgr start
    Starting up the Status Monitor daemon
        /usr/sbin/rpc.statd
    Starting up the lock manager daemon
        /usr/sbin/rpc.lockd
# /sbin/init.d/nfs.server start
    Starting NFS SERVER subsystem

    Reading in /etc/dfs/dfstab
    Starting up the mount daemon
        /usr/sbin/rpc.mountd
    Starting up the NFS server daemon
        /usr/sbin/nfsd
      Starting up nfsmapid daemon
        /usr/sbin/nfsmapid

Saturday, June 7, 2014

Xmanager not able to see hpux host

Do following steps :-

# /sbin/init.d/dtlogin.rc start
# /usr/dt/bin/dtconfig -e
done
desktop auto-start enabled.
#


Wednesday, July 24, 2013

VNC HP-UX Cannot establish any listening sockets

Error while starting the VNC

#vncserver :1


XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't already running


Solution:

Check in  /var/spool/sockets/X11 any old unused sockets ( above case socket number will be 1 ) and remove that one.


Thursday, June 20, 2013

Find tape drive serial number HP-UX


To find out the serial number of tape drive connected to HP_UX server.

1. use devbra 

#/opt/omni/lbin/devbra -dev

2. use cstm

#echo "map; wait; selall; wait; info; wait; infolog; view; done" | cstm > /tmp/cstm.txt

Read through the output  you will get  details of tape drive like this.

Hardware path: 0/3/0/0/0/0.3.10.255.0.0.0


Device Qualifier:    HPUltrium
Product ID:          Ultrium 4-SCSI     Hardware Path:
0/3/0/0/0/0.2.10.255.0.0.0
Device Type:         SCSI Tape          Logical Unit Number:    0
Vendor:              HP                 Product Rev Level:      H58W
Firmware Revision:   012.847            Tape Load Count:        0
Correctable Errors:  0                  Uncorrectable Errors:   0
Mfg Date Code:       N/A                Servo Revision:         H/W.REV
Serial Number:       HU18283HG1
Compression Status:  Enabled            Compression Ratio:
                                                  [instant]     N/A
                                                  [average]     1.0 : 1
Capacity [M Byte]:   0
Drive Status:        Good


3.  use fcmsutil

fcmsutil   HBA_PATH get remote all.

This will show the serail no of tape driver on the port where it connected.


Thursday, June 6, 2013

ssh: connect to host [server] port 22: Connection refused HP-Ux


  
1.  Verify how many  "/opt/ssh/sbin/sshd" process  running in the server. If more than once process is running kill  all the "/opt/ssh/sbin/sshd" process and start ssh using /sbin/init.d/secsh start.

2. Verify that "/opt/ssh/sbin/sshd"  process is running. if not start sshd process using "/sbin/init.d/secsh start"

3. If you can connect to sshd using localhost in the server, then check for any firewall blocking access to sshd port in outside network.

Monday, May 20, 2013

Rescue Mode suse linux - Reset root password , repair file systems.




   Boot server from the installation CD.

Then select any installation method or Rescue System.

At the first installation screen when selecting language, press ctrl-alt-f2 to open a virtual console. 
Note: If you selected Rescue System, select your keyboard language and then a Rescue Login prompt should appear. Login as root.

Enter below to list the partitions. Locate the Linux root partition.

fdisk -l

Enter
mount /dev/sda3 /mnt
(replace sda3 with the device name for the Linux root partition identified in the previous step).

If  its lvm then use appropriate device  
Example: mount /dev/vg00/lvol1 /mnt

Then Run below to make the device files available

mount -o bind /dev  /mnt/dev 

 (this is needed for access to the urandom device which may be used by the passwd command below).
Enter
chroot /mnt
Now enter
passwd root
and reset the root password.

If you want mount all file sytem,
mount -av
Type
exit
to leave the chroot environment.
Reboot the system 

If  lvm disks  not visible run below.

# lvm
# pvscan
# vgscan
# lvscan
# vgchange -ay
# exit
# e2fsck -f /dev/vg00/lvol1

If  keystrokes getting repeated in remote  ILO console below is the solution

DESCRIPTION
When using HP Integrated Lights-Out 3 (iLO 3) Integrated Remote Console (IRC) over a slow or congested network, the keystrokes may repeat several times even though the key is not pressed. For example, typing "ahs.bat" may result in "ahs.bbbbbbbbat."
When the network connectivity is slow or lagging, the "key up" command may not be delivered to iLO 3 in a timely manner after the "key down" command is sent. This can cause the host server to believe that the key is still pressed down even though the key has been released.
SCOPE
Any HP ProLiant server with Integrated Lights-Out 3 (iLO 3) while using Integrated Remote Console (IRC) over a slow or congested network.
RESOLUTION
To prevent this from occurring, improve the bandwidth and reduce latency between the Integrated Remote Console (IRC) client system and the host operating system. Some common sources of latency are running over a Virtual Private Network (VPN) or running over a wireless network connection.
As a workaround, adjust the key repeat rate within the server operating system. For example, on a Windows Server, performing the following steps:
Open Control Panel.
Open Keyboard.
In the Character Repeat section, lower the Repeat Rate until repeat keys are no longer sent. Slower networks will require a slower repeat rate.