Sponsored Content
Operating Systems HP-UX Hitachi Device Manager Agent for HPUX Post 302736555 by cerber0 on Tuesday 27th of November 2012 01:12:09 PM
Old 11-27-2012
I remember that in the recent versions if you download de Hitachi Command Suite (Before Device Manager) Server you can run the setup and this open a page that show the links to obtain the agents.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Device Manager?

I am a complete noob trying to learn my way around Solaris. I need to learn it for work so I though the best way to do that would be to go ahead and load it up and play with it. I downloaded the latest version from the Sun website and put it on a box with an AMD processor and Via Chipset KM400. ... (3 Replies)
Discussion started by: mugicha
3 Replies

2. Filesystems, Disks and Memory

hpux vg accessible but device files missing!

Hi all, I am looking at a MC cluster comprised of 2 nodes. There is a package named backup which does nothing more than mount a VG. At one point we noticed errors in syslog that look like this: cmclconfd: Could not access device file /dev/dsk/c20t0d0: No such file or directory There are... (1 Reply)
Discussion started by: mariusp
1 Replies

3. Solaris

Solaris & Hitachi identify

Hello, Is there anyway to tell which set of Hitachi array the disks belong to? I'm remotely located so I cannot do the physical check. The possible Hitachi arrays are: AMS1000 and 9570 This is what I see on the format: 2. c2t50060E800475EA02d1 <HITACHI-OPEN-V*9-SUN-5007 cyl 65533 alt 2... (0 Replies)
Discussion started by: kiem
0 Replies

4. UNIX for Dummies Questions & Answers

snmp manager and agent

Hi, I'm reading net-snmp, using Unix (Solaries) and C language ... - I can manipulate variable (managed object) declared in agent, but the manager can't see that ... it only see the initialization and the value which it ulters using snmpset ... Ex: Agent: static int ... (0 Replies)
Discussion started by: zainab
0 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. HP-UX

Hitachi arrays to HP-UX 11.11

We have 2 servers (L1000 and rp7410) running 11.11. We would like to hook them up to either a Hitatchi AMS 2500 or Hitachi USPV via fiber channel. I need to what drivers I need for this and if it will work. Oh, they are using HP Tachyon XL2 Fiber Channel Mass Storage Adapters. Thanks, Bill (1 Reply)
Discussion started by: wsmcelroy
1 Replies

7. Solaris

Hitachi Airis Mate 2007, Unix 5.0

Hello everyone! Today we have a problem and decided to ask people on this forum maybe someone can help. At our medical center we have an Hitachi Airis Mate MRI system, yom 2007 with Unix OS (don't know exactly the version). As usually, in the morning we started up the system normally and it... (1 Reply)
Discussion started by: cmdp
1 Replies

8. AIX

Aix and Storage Hitachi

Hello everyone I would like to hear your opinions about Aix 6.1 and Aix 5.3 with Storage Hitachi the model is USP VM. We buy it and I want to know day to day task with this storage and Aix. Thanks for your comments. Best wishes for this 2010 (2 Replies)
Discussion started by: lo-lp-kl
2 Replies

9. Hardware

Hitachi HD issues

I have an adapter that can read ide and sata HD's. When the drive is good it lights up green and when its bad it lights up red. I have used the adapter already to read about 10 other HD's with no problem. When I got to the hitachi HD it lights up green but I can't see what is on it or even format.... (0 Replies)
Discussion started by: cokedude
0 Replies
FS_GETCLIENTADDRS(1)					       AFS Command Reference					      FS_GETCLIENTADDRS(1)

NAME
fs_getclientaddrs - Displays the client interfaces to register SYNOPSIS
fs getclientaddrs [-help] fs gc [-h] fs getcl [-h] DESCRIPTION
The fs getclientaddrs command displays the IP addresses of the interfaces that the local Cache Manager registers with a File Server when first establishing a connection to it. The File Server uses the addresses when it initiates a remote procedure call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by the Cache Manager). There are two common circumstances in which the File Server initiates RPCs: when it breaks callbacks and when it pings the client machine to verify that the Cache Manager is still accessible. If an RPC to that interface fails, the File Server simultaneously sends RPCs to all of the other interfaces in the list, to learn which of them are still available. Whichever interface replies first is the one to which the File Server then sends pings and RPCs to break callbacks. fs_setclientaddrs(1) explains how the Cache Manager constructs the list automatically in kernel memory as it initializes, and how to use that command to alter the kernel list after initialization. CAUTIONS
The File Server uses the list of interfaces displayed by this command only when selecting an alternative interface after a failed attempt to break a callback or ping the Cache Manager. When responding to the Cache Manager's request for file system data, the File Server replies to the interface which the Cache Manager used when sending the request. If the File Server's reply to a data request fails, the file server machine's network routing configuration determines which alternate network routes to the client machine are available for resending the reply. The displayed list applies to all File Servers to which the Cache Manager connects in the future. It is not practical to register different sets of addresses with different File Servers, because it requires using the fs setclientaddrs command to change the list and then rebooting each relevant File Server immediately. The displayed list is not necessarily governing the behavior of a given File Server, if an administrator has issued the fs setclientaddrs command since the Cache Manager first contacted that File Server. It determines only which addresses the Cache Manager registers when connecting to File Servers in the future. The list of interfaces does not influence the Cache Manager's choice of interface when establishing a connection to a File Server. OPTIONS
-help Prints the online help for this command. All other valid options are ignored. OUTPUT
The output displays the IP address of each interface that the Cache Manager is currently registering with File Server processes that it contacts, with one address per line. The File Server initially uses the first address for breaking callbacks and pinging the Cache Manager, but the ordering of the other interfaces is not meaningful. EXAMPLES
The following example displays the two interfaces that the Cache Manager is registering with File Servers. % fs getclientaddrs 192.12.105.68 192.12.108.84 PRIVILEGE REQUIRED
None SEE ALSO
fileserver(8), fs_setclientaddrs(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FS_GETCLIENTADDRS(1)
All times are GMT -4. The time now is 06:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy