I changed out one the two FC switches. It appears my paths have all come back up except for this one "dac0" which appears as "missing" and I'm not having any luck getting rid of that... All of the disks came back fine, just dac0 is missing. This output is from my lpar, not the underlying VIO server. Any ideas?
Hi , Migrating AIX 4.3.3 ML10 to 5.3 ML1 (retaining 32 bit)
after successfully going through 5 of the 5.3 Install CD's. After "All fileset's processed successfully " message I was told that system would reboot and then I would get prompted for setting TERm type ( i have an ascii ibm3151) and... (1 Reply)
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Hello All,
We want to upgrade our 44p Model 270 from AIX 5.2 to 5.3. This is a standalone devlopment server but downtime is something we don't want because we have a short development deadline looming. I have no tape drive to make backups to. I myself am a developer and don't have any... (4 Replies)
Hi,
redbook documentation is telling that IY17981 fix is required for aix 4.3.3 to aix 5L migration. But there is no mention about that fix in any ML installation packages.
- My system is ML11 :
oslevel –r
4330-11
- But xlC.rte is on wrong version :
lslpp -L xlC.rte
xlC.rte ... (3 Replies)
Hello gurus,
I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place.
Environment: Migrating from CX4 to VMAX - using OR/Hot Pull.
Here are the steps I have put together - HPUX gurus please... (5 Replies)
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.
Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong)
1.... (0 Replies)
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Hi,
I am very new to HP-UX, and we're going to be doing a SAN migration.
We're going to take down the machine, and zone it to the new SAN.
My question is, will the device names change and will that interfere with the LVM?
If the new disks come in with different device names, how would I... (3 Replies)
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
LEARN ABOUT HPUX
norewind_close_disabled
norewind_close_disabled(5) File Formats Manual norewind_close_disabled(5)NAME
norewind_close_disabled - determine whether access to tape device special files without the no-rewind-on-close option is allowed
VALUES
Default
Allowed values
DESCRIPTION
Note: this tunable was named in releases prior to HP-UX 11i v3.
This tunable notifies the tape driver whether it should allow access to device special files without the no-rewind-on-close option. When
this tunable is on, the tape driver will fail any open on a tape device special file that does not have the no-rewind-on-close option (that
is, or with a status of
The tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files
without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from
HP-UX systems via standard tape commands like which would corrupt a backup in process.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Tunable Be Turned On?
This tunable should be turned on if the system is going to be used in a SAN tape backup solution configuration.
What Are the Side Effects of Turning the Tunable On?
The tape driver will fail any open to a tape device special file that does not have the no-rewind-on-close option with a status of This
behavior prevents the usage of any tape device special file without the no-rewind-on-close option.
When Should the Tunable Be Turned Off?
This tunable should be turned off if the system is not part of a SAN tape backup solution configuration or the system utilizes will not
function unless it has access to device special files without the no-rewind-on-close option.
What Are the Side Effects of Turning the Tunable Off?
A rewind may be issued accidentally from this system on close, possibly corrupting a backup being issued from another system on the SAN.
What Other Tunables Should Be Changed at the Same Time?
None.
EXAMPLES
Query the current value of the tunable:
Set the value of the tunable to
To save the value of the tunable across reboots:
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 Hewlett-Packard.
SEE ALSO scsi_tape(7), scsimgr_estape(7).
Tunable Kernel Parameters norewind_close_disabled(5)