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)
Using Solaris 10 with Veritas Storage Foundation running. I want to copy all contents from DISKA LUN1 to DISKB LUN2. What would be the command syntax to do this? (0 Replies)
I have a general question regarding Zone Migration.
I have an older system that is currently running a zone configured with ProFTPD & SSL.
If I want to migrate or clone that zone to another (much newer) system, will I still have to setup & configure ProFTPD & SSL on the new system? (3 Replies)
Hey everyone.
I am working on designing a logging solution for a deployment we have going out in a few months. Right now we have a single storage head end, connected via fibre to a SAN. Basically the plan is to create a number of smaller LUNs on the SAN, and then use LVM2 to handle concatenating... (5 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)
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'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (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
hostname
hostname(1) General Commands Manual hostname(1)NAME
hostname - set or display name of current host system
SYNOPSIS
[name_of_host]
DESCRIPTION
The command displays the name of the current host, as given in the system call (see gethostname(2)). Users who have appropriate privileges
can set the hostname by giving the argument name_of_host; this is usually done in the startup script The name_of_host argument is
restricted to characters as defined in
The system might be known by other names if networking products are supported. See the node manager documentation supplied with your sys-
tem.
WARNINGS
If the name_of_host argument is specified, the resulting host name change lasts only until the system is rebooted. To change the host name
permanently, run the special initialization script (see
Many types of networking services are supported on HP-UX, each of which uses a separately assigned system name and naming convention. To
ensure predictable system behavior, it is essential that system names (also called host names or node names) be assigned in such a manner
that they do not create conflicts when the various networking facilities interact with each other.
The system does not rely on a single system name in a specific location, partly because different services use dissimilar name formats as
explained below. The and commands assign system names as follows:
+--------------+---------------+----------------+---------------------------+
|Node Name | Command | name Format | Used By |
+--------------+---------------+----------------+---------------------------+
|Internet name | hostname name | sys[.x.y.z...] | ARPA and NFS Services |
|UUCP name | uname -S name | sys | uucp and related programs |
+--------------+--------------+---------------+-----------------------+--|Node-+-Name-------|Command-------+ |name Format |Used By
| +--------------+--------------+---------------+-----------------------+ |Internet name |hostname name |sys[.x.y.z...] |ARPA and NFS Ser-
vices | |UUCP name |uname -S name |sys |uucp, related programs | +--------------+--------------+---------------+--------
--------------+
where sys represents the assigned system name. It is recommended that sys be identical for all commands and locations and that the
optional follow the specified notation for the particular ARPA/NFS environment.
Internet names are also frequently called host names or domain names (which are different from NFS domain names). Refer to hostname(5) for
more information about Internet naming conventions.
Whenever the system name is changed in any file or by the use of any of the above commands, it should also be changed in all other loca-
tions as well. Other files or commands in addition to those above (such as if used to circumvent for example) may contain or alter system
names. To ensure correct operation, they should also use the same system name.
System names are normally assigned by the script at start-up, and should not be altered elsewhere.
Setting a hostname of more than 64 bytes is possible only with the appropriate configuration options enabled. It is strongly recommended
that all related documentation be completely understood before setting a larger hostname. A hostname larger than 64 bytes can cause anoma-
lous or incorrect behavior in applications which use the command or the system function to access the name.
AUTHOR
was developed by the University of California, Berkeley.
SEE ALSO uname(1), gethostname(2), sethostname(2), uname(2), hostname(5), nodehostnamesize(5).
hostname(1)