Sponsored Content
Full Discussion: Ignite issue on HPUX server
Operating Systems HP-UX Ignite issue on HPUX server Post 302266695 by DustBunny on Wednesday 10th of December 2008 09:15:02 PM
Old 12-10-2008
My apologies,

I don't think that should work in this case. I've tried it on my server yesterday. Things go non related. But, proceed checking hardware.

-DB
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

without an ignite server ??

system: HP-UX 10.20 with HFS mounted. How can I convert the HFS to VxFS without an ignite server ? Is this possible ? thanks simon2000 (4 Replies)
Discussion started by: simon2000
4 Replies

2. UNIX for Advanced & Expert Users

an ignite server for Solaris 8 ?

I know and used an ignite server for hp-ux, but is there such a beast for Solaris flavour of unix ? thanks simon (1 Reply)
Discussion started by: simon2000
1 Replies

3. HP-UX

HP-UX Ignite server

Sorry if this has been asked and answered, but I can't find this particual problem. I've had an Ignite server running for years on a small internal network with images we load on daily basis. Tried to load two servers, L2000 and C3600 , both with same problem. # boot lan.192.168.2.2 install ... (0 Replies)
Discussion started by: ddeblance
0 Replies

4. HP-UX

HPUX model scirpt issue

hi, I am using HPUX 11.31(Itanium) and HP 5100 printer. I am using PCL5.nloo model script present in HPUX by default to print to printer. I am finding issues in printing paper sizes and few other options. Description of the problem: When i give a print with option "half" and "Legal"... (4 Replies)
Discussion started by: meeraramanathan
4 Replies

5. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

6. Shell Programming and Scripting

issue while auto login using .ssh for HPUX

Hi, While trying to supress password prompt using ssh. I have added .ssh folder manually and generated public key and added to authorized_keys file in the remote machine. But still it's prompting for passwords with the following message: Permission denied... (5 Replies)
Discussion started by: 116@434
5 Replies

7. HP-UX

Ignite-ux and dhcp server Linux

I try to start a integrity vm machine using ignite-ux and my usual dhcp server on linux. Ip of server ignite is =192.168.0.16 Ip of dhcpd is = 192.168.0.2 Ip of client vm = 192.168.0.18 I try to boot from lan Booting over the network Loading.: lanboot Client MAC Address: XXXXXXXXXX ..... (5 Replies)
Discussion started by: Linusolaradm1
5 Replies

8. HP-UX

HPUX nsswitch.conf issue

Hi all, There wasn't nsswitch.conf file in my HPUX server. So I copied /etc/nsswitch.files to /etc/nsswitch.conf and changed the content like below. passwd: compat group: compat hosts: files dns nis ipnodes: dns files services: nis files networks: nis... (2 Replies)
Discussion started by: sembii
2 Replies

9. HP-UX

Ignite recovery issue.

On one of the Hpvm server when I try to do the ignite recovery it aborts after recovering only 30 % of the archive. I do not have any other archive backup besides this. Even after restoring the 30 archive I could see that I am able to login to that server althoug ssh and other functionalities... (9 Replies)
Discussion started by: kpatel786
9 Replies
iobind(1M)																iobind(1M)

NAME
iobind - bind a driver to a device SYNOPSIS
instance] DESCRIPTION
The command may be used to perform online unbinding of a device LUN hardware path from its current driver and binding a new driver to it. As part of the binding operation, the specified driver will be bound to the LUN hardware path and also to its corresponding legacy hardware paths. The hardware path specified as the argument to the option must be of the form 64000/0x/0x. The driver name specified with the option will be bound to the LUN and legacy hardware paths. The optional option specifies an instance number to be assigned to the device associated with the hardware path. If this option is not used, the device will be assigned a new instance number in the new driver's class. The optional forces the binding to occur at the next reboot if it cannot be done online. The device must not be in use while the unbind operation is performed. The driver must support online unbinding and binding. If either of these requirements is false and the option is not given, the user will be asked if the binding can take effect at the next reboot. The user is given the option to proceed or not. If a driver supports online unbinding and binding, then after completes, a device will have one of the following software states as shown by the command: The specified driver was successfully bound to the hardware path. The specified driver cannot be used to claim the hardware at the specified hardware path. The device at the address is responding, but it is in an error state. The device at the specified hardware path is no longer responding. The specified hardware path is locked. Try again later. The driver failed. Options recognizes the following options: Force the binding even though a driver does not support online unbinding and binding or the device is in use. In this case, the binding will take effect at the next reboot. The LUN hardware path of a device must be of the form 64000/0x/0x. The instance number to be assigned to the device. The name of the driver that the LUN and legacy hardware paths are to be bound to. RETURN VALUE
Exit values are: Successful completion. An error condition occurred. EXAMPLES
Unbind the driver bound to the device at hardware path and bind the device to Use the default instance number of the driver's class. Unbind the driver bound to the device at hardware path and bind the device to Assign it the instance number Do a forced binding. If the driver does not support online binding or the device is busy, the binding will be deferred till next reboot. WARNINGS
The and commands should not be run at the same time because both commands attempt to bind drivers. In particular, there may be a short window while will leave a hardware path unbound. If runs during that window, it may bind a different driver to that hardware path. If this happens, must be executed again to bind the desired driver. may be executed only by the superuser. SEE ALSO
ioscan(1M), intro(7). iobind(1M)
All times are GMT -4. The time now is 08:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy